On Thursday 18 December 2008, Alex Samad <alex@samad.com.au> wrote about 'Re: LVM reorganization': >On Thu, Dec 18, 2008 at 01:31:18AM -0600, Boyd Stephen Smith Jr. wrote: >[snip] > >> Shrinking the LV is probably the most dangerous part. You don't want >> to > >1 word > >backup 3 words: 4 TB /home I couldn't scrape together 4 TB of extra HD space right now. Even if I could /home would just get bigger anyway. It would take more DVDs than are in the house to backup the system, and when burning that many DVDs, you can virtually guarantee at least one coaster. Sorry, it's not reasonable for me to backup each time I change my LVM settings. It's also not really necessary, even in this case of shrinking. After the LV is shrunk, an fsck of the filesystem should warn you if the size of the LV is too small (IIRC, fsck.reiserfs and fsck.ext[23] do and I've never used JFS or XFS). If you get that notice, avoid making changes to the filesystem and instead use vgcfgrestore to roll back to the earlier LV size. Then fsck and fix any errors; there won't be any if you vgcfgrestored correctly and did the first fsck early enough. Luckily for me, I've learned that ReiserFS and LVM have the same idea of "G" so a resize_reiserfs -s 50G followed by a lvreduce -L50G make the filesystem and the LV the same size. I don't even always fsck the filesystem at this point -- I know my LV is just the right size. (Since I don't go down to single-user mode all that often, it is a good time to go ahead and fsck all my filesystems, though.) -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss03@volumehost.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.org/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.