On Thu, Nov 08, 2007 at 04:51:00PM -0700, Mark Post wrote: > That's going to depend largely on what is making up the underlying block > device. If it's an LVM Logical Volume, it's very easy: > - Unmount the file system > - lvreduce the logical volume > - e2fsck -f /dev/vgname/lvname > - resize2fs /dev/vgname/lvname > - Remount the file system
I'm sure Mark meant the proper order for these operations: 1. umount 2. fsck 3. resize2fs 4. lvreduce 5. mount For those that like to feel a little safer that resize2fs and lvreduce are speaking the same units, do resize2fs smaller than your target size, lvreduce to the actual size then resize2fs again, without specifying a size. resize2fs does the right thing of using the max size if no size is specified. In reality though, if you have a file system you need to reduce significantly, it's probably a better idea to remake&restore it. $.02 -- Bill Carlson -- Systems Administrator [EMAIL PROTECTED] | Anything is possible, HCIS | given time and money. University of Iowa Hospitals and Clinics | Opinions are mine, not my employer's. | ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
