fsck and raidtools

Sy Ali sy1234-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Thu Sep 7 23:41:21 UTC 2006


On 9/7/06, Lennart Sorensen <lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org> wrote:
> It looks more to me like someone did and mkfs on the device, then
> decided to make it a raid device, and the raid mirrored that original
> formatting (minus the raid superblock) onto both devices.  This means
> part of the filesystem was overwritten of course by the raid superblock.
> One must always make a new filesystem after creating a raid, even if it
> looks like you can actually mount the old filesystem that was on one of
> the devices before hand.
>
> So in short, I believe someone made a mistake while setting up the raid
> and that the drive now has a slightly corrupted filesystem on it and
> should be re-mkfs'd to fix it.  I have certainly never had fsck fail on
> an md device before.

I wondered what was going on and restored from backups and restored
the setup to a non-raid state.  Now that I understand this I can set
it back up the way it was intended.  =)

Thanks..
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wini/Mailing_lists





More information about the Legacy mailing list