Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am transitioning from a SAN admin to Linux admin, so hopefully this is not too dumb of a question. I need to extend a FS, which has SAN attached PV in its Vol Group.
Can I just extend the LUN from Storage array ( NetApp ) or do I need to assign a new LUN and add that to existing Vol group and then extend the Volume ?
Usually expanding LUN would be done on the NetApp, then the filesystem expanded by the host.
This allows the NetApp to optimize the storage (even to copying the blocks if necessary) without affecting the data.
Now doing something like changing the stripe width on the NetApp would be a different thing. I don't know if the current NetApp OS knows how to copy a lun and still get the block addressing right. I believe it would have to copy the lun to a new one for that to work. Adding to a lun (without changing the striping) should be easy - just append the extension to the end of the existing LUN. I believe the documentation for the NetApp would have the instructions (though the specific instructions might be hard to find - I found their documentation fairly complete, but with some things scattered).
One problem with expanding the filesystem is that some things don't necessarily get expanded (inode table I think, but not sure). If the filesystem is xfs, no problem as the inode list is already dynamically expandable (which is why you may see huge inode numbers - I think they are also the block number of the inode).
NOTE: It has been over 5 years since I worked with NetApp storage devices.
As always, be sure you have something for a backup. Sometimes it is easier and safer to create a new bigger lun, create the new filesystem, and copy the old filesystem. The old lun is the backup...
Note you can't "just add" it - regardless of whether you extend the LUN or add a new one. The new space needs to be formatted for LVM use (pvextend or pvcreate), then the vg extended, then the lv. And before all that you may need to re-scan the bus to make the new/extended storage seen by Linux.
Redhat have some beaut manuals on this.
Thanks for the replies. NetApp's OS will handle the block sizes, and this server already has NetApp LUNs presented.
The previous system admin has been adding new LUNs and then add them to the VG. The only down side with that is now we have several physical volumes to manage.
Now If I can just figure out how to re scan the scsi bus without having to reboot the box :-)