[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <498CBD09.4020301@redhat.com>
Date: Fri, 06 Feb 2009 17:43:21 -0500
From: Ric Wheeler <rwheeler@...hat.com>
To: "J.D. Bakker" <jdb@...tmaker.nl>
CC: Ric Wheeler <rwheeler@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: Recovering a damaged ext4 fs - revisited.
J.D. Bakker wrote:
> At 17:15 -0500 06-02-2009, Ric Wheeler wrote:
>> J.D. Bakker wrote:
>>> Hi,
>>>
>>> My 4TB ext4 RAID-6 has just become damaged for the second time in
>>> two months. While I do have backups for most of my data, it would be
>>> good to know if there is a recovery procedure or a way to avoid
>>> these crashes. The symptoms are massive group descriptor corruption,
>>> similar to what was mentioned in
>>> http://thread.gmane.org/gmane.comp.file-systems.ext4/10844 and
>>> http://article.gmane.org/gmane.comp.file-systems.ext4/11195 .
>> What kind of RAID 6 device are you using? Is it MD raid or some
>> vendor array?
>
> md, as shown in the linked config and dmesg.
>
>>> http://lartmaker.nl/ext4/kernel-config.txt
>>> http://lartmaker.nl/ext4/dmesg.txt
>>> http://lartmaker.nl/ext4/lspci.txt
>>> http://lartmaker.nl/ext4/proc-mdstat.txt
>>> http://lartmaker.nl/ext4/proc-partitions.txt
>
> JDB.
RAID6 is not that new, but it is newer than MD raid5. Does RAID5/6
handle the write barriers correctly these days? I think that barriers
are enabled only for RAID1 which means that your disks might be holding
up lots of volatile data that will go "poof" if you power off or reboot.
You can "fix" this by disabling the write cache on your drives, but you
will have a performance hit (at least for S-ATA drives).
Ric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists