From: Marc Lehmann <pcg@schmorp.de>
To: jpearson@oasissystems.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange ext3 corruption problem on 2.6.x
Date: Mon, 15 Mar 2004 04:41:25 +0100 [thread overview]
Message-ID: <20040315034125.GA5295@schmorp.de> (raw)
In-Reply-To: <20040314222929.GA23106@mark>
On Mon, Mar 15, 2004 at 08:59:29AM +1030, jpearson@oasissystems.com.au wrote:
> 'r/o' by the RAID layer, presumably unbeknownst to VFS; are you
> *sure* that your array is still up and 'good' when you get this
> message?
As I said, there are no other messages, so if there is a problem (cabling,
disk-i/o etc.), then the kernel doesn't know it either (usually the kernel
it quite loud in this condition).
The array also comes up clean and synced. And the reiserfs partition on
the same lv doesn't have any problems (wether this means that reiserfs
doesn't suffer from this bug or wether reiserfs is just unable to detect
it is, of course, a different question).
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next parent reply other threads:[~2004-03-15 3:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040314222929.GA23106@mark>
2004-03-15 3:41 ` Marc Lehmann [this message]
2004-03-18 7:25 ` strange ext3 corruption problem on 2.6.x Pavel Machek
2004-03-23 7:33 John Pearson
2004-03-23 7:54 ` Andrew D Kirch
[not found] <1zRh6-2V6-9@gated-at.bofh.it>
[not found] ` <1zRh6-2V6-7@gated-at.bofh.it>
2004-03-15 23:25 ` Thorild Selen
-- strict thread matches above, loose matches on Subject: below --
2004-03-13 0:47 Marc Lehmann
2004-03-13 2:34 ` Andrew Morton
2004-03-13 2:40 ` Marc Singer
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=20040315034125.GA5295@schmorp.de \
--to=pcg@schmorp.de \
--cc=jpearson@oasissystems.com.au \
--cc=linux-kernel@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