From: Eric Sandeen <sandeen@redhat.com>
To: "Krzysztof Kosiński" <tweenk.pl@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Massive corruption on RAID0
Date: Tue, 30 Jun 2009 10:33:57 -0500 [thread overview]
Message-ID: <4A4A3065.4020202@redhat.com> (raw)
In-Reply-To: <298610bb0906290812t249c7e52l80e57af36bd0e80c@mail.gmail.com>
Krzysztof Kosiński wrote:
> W dniu 29 czerwca 2009 05:30 użytkownik Eric Sandeen
> <sandeen@redhat.com> napisał:
>> Is the super.bin above from before the fiddling you did (i.e. right
>> after the power loss?)
> Yes, it's before I started my recovery attempts, though mount and
> e2fsck -p were run on it during the boot process before I removed it
> from fstab.
>
>> The superblock is marked with errors, I wonder
>> if there were other errors reported on the filesystem prior to the power
>> loss; you might check your logs ...
> I checked and it seems there were no errors until the power failure.
> By the way, is there some way to have RAID0-like functionality with
> write barriers?
Mirrors can pass barriers, IIRC, but not stripes (IIRC...) - I don't
know if any work is being done to address this.
I wonder if there's any chance that your raid was reassembled
incorrectly....
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-30 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 0:38 Massive corruption on RAID0 Krzysztof Kosiński
2009-06-29 3:30 ` Eric Sandeen
2009-06-29 15:12 ` Krzysztof Kosiński
2009-06-30 15:33 ` Eric Sandeen [this message]
[not found] ` <87f94c370906300942p7c5f576cgbb8c065625cf1716@mail.gmail.com>
2009-06-30 16:46 ` Eric Sandeen
2009-06-30 18:28 ` Mike Snitzer
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=4A4A3065.4020202@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tweenk.pl@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.