From: Bill Davidsen <davidsen@tmr.com>
To: "Rustedt, Florian" <florian.rustedt@smartnet.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Journalling filesystem corruption fixed in between?
Date: Fri, 05 Oct 2007 11:51:17 -0400 [thread overview]
Message-ID: <47065D75.7040802@tmr.com> (raw)
In-Reply-To: <735D322AED9CD711BE53000476917CD0029728C3@NT-SERVER-5>
Rustedt, Florian wrote:
> Hello list,
>
> some folks reported severe filesystem-crashes with ext3 and reiserfs on
> mdraid level 1 and 5.
>
> Is this safe now? Or should i only use non-journalling-filesystems on
> software-raid-devices?
>
I have been using swRAID since it was an experimental patch, and haven't
seen any indication that this is true. Clearly any f/s will be subject
to error on bad hardware.
Sounds like an urban myth to me!
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2007-10-05 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 11:04 Journalling filesystem corruption fixed in between? Rustedt, Florian
2007-10-02 11:12 ` Justin Piszcz
2007-10-03 7:19 ` Michael Tokarev
2007-10-05 15:51 ` Bill Davidsen [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=47065D75.7040802@tmr.com \
--to=davidsen@tmr.com \
--cc=florian.rustedt@smartnet.de \
--cc=linux-raid@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).