On Sunday 21 December 2008, "M.Lewis" <cajun@cajuninc.com> wrote about 'Re: e2fsck /dev/md0 issues': >Boyd Stephen Smith Jr. wrote: >> I assume that /dev/md0 knows it's size, so the filesystem superblock is >> bad and you should correct it by resizing the filesystem. > >Is there a way to know for certain that /dev/md0 knows the correct size? Well, not that I know of off the top of my head. Perhaps there is some "check" mode to mdadm? Even if it were somehow "wrong" it would still be right. Let me explain. The md driver that determines the devices size is the same driver that controls all reads and writes to the device. It won't let you (or a filesystem) read/write into areas it doesn't think are there, based on the size it reports. So, even if the size it reports is calculated erroneously, you (or a filesystem) won't be able to read or write to the device outside of the bounds implied by the reported size. In short, unless you have some good reason to suspect your md driver is broken, trust it. >Maybe what I should do is break the array and start over? Making sure >that e2fsck on both drives is good to go beforehand of course. > >Maybe that is a more drastic action than is needed though. Yep. You just need to resize your filesystem to the correct size, as reported by the /dev/md0 device and suggested by my earlier email. -- 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.