From: Ric Wheeler <rwheeler@redhat.com>
To: "J.D. Bakker" <jdb@lartmaker.nl>
Cc: Ric Wheeler <rwheeler@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: Recovering a damaged ext4 fs - revisited.
Date: Fri, 06 Feb 2009 17:43:21 -0500 [thread overview]
Message-ID: <498CBD09.4020301@redhat.com> (raw)
In-Reply-To: <p06240530c5b26b5a174c@[10.1.5.33]>
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
prev parent reply other threads:[~2009-02-06 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 3:06 Recovering a damaged ext4 fs - revisited J.D. Bakker
2009-02-06 4:02 ` Eric Sandeen
2009-02-06 12:18 ` J.D. Bakker
2009-02-06 15:23 ` Eric Sandeen
2009-02-06 6:29 ` Andreas Dilger
2009-02-06 12:23 ` J.D. Bakker
2009-02-06 21:44 ` Andreas Dilger
2009-02-06 22:15 ` Ric Wheeler
2009-02-06 22:34 ` J.D. Bakker
2009-02-06 22:43 ` Ric Wheeler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=498CBD09.4020301@redhat.com \
--to=rwheeler@redhat.com \
--cc=jdb@lartmaker.nl \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).