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.
Pretty new to RHEL. Running RHEL 5.5 and I have an iSCSI (ext-3) connection to an EqualLogic SAN group with a 2.50 TB volume. I have a second 5.0 TB volume on the SAN then is free. I'd like to drop the 5.0 TB volume and resize the 2.50 TB volume to take advantage of the full capacity.
After modifying the SAN capacity to use the full space, what are the proper comman line steps on the Linux server to rescan/resize the volume? Thanks in advance.
The problem is not the expansion, that shouldn't be a problem for the SAN. The problem is resizing the existing filesystems. That depends on the filesystem already existing.
Some of the filesystems (ext2 and I think 3) have fixed size inode tables. Just expanding the storage will get you more data space, but you still can't add more inodes. filesystems like ext4/xfs/btrfs, also allow inode tables to be expanded as needed.
Other than that there are a number of references (google is your friend) on doing that. As always, backups are essential - just in case something goes wrong.
BTW, be sure the "new space" is added to the existing space, and not the otherway around.
It is possible to do it that way, but the existing filesystem has to be relocated (as in copied to the new beginning) before it will even work.
Thank you for the quick response. I believe we just did a backup but I wouldn't make a change like this without one. The disk is not mounted to /dev/sdX, but its mounted to /dev/dm-4. My assumption is this won't make a difference? Last question, no unmounting is required? This process seems awefully short for a Linux process.
You said ext3, so yes, this should be able to all be done online.
If dm-4 is a multipath device, you need to rescan all underlying sdX devices. If it's some other sort of device mapped disk, you may need extra steps.
If LVM is in use, after expanding the LUN on the SAN and making Linux detect it, you need to pvresize the physical volume, then lvresize the LV, then you can resize2fs the filesystem.
Thank you all again for the input. Here's my working process. Time to complete was about an hour.
From SAN Web Interface
1. Make sure you have a good backup
2. Remove 5.0 TB volume via EqualLogic web interface.
3. Resize 2.5 TB volume via EqualLogic web interface.
This step may not be necessary, but if you receive a "umount: <path> : device is busy" message, it may be necessary to kill one or all processes for a user
From Linux Server
4. Un-mount the file system – umount /dev/eql/volume
5. Run File System Check – fsck –f /dev/eql/volume (about 30 - 45 min)
6. Run Resize - resize2fs /dev/eql/volume (about 15 min)
7. Mount the file system – mount /dev/eql/volume
8. Run a df -h and verify new space is available and all data is intact