From: Pavel Machek <pavel@ucw.cz>
To: jpearson@oasissystems.com.au, linux-kernel@vger.kernel.org
Subject: Re: strange ext3 corruption problem on 2.6.x
Date: Thu, 18 Mar 2004 08:25:28 +0100 [thread overview]
Message-ID: <20040318072521.GB597@openzaurus.ucw.cz> (raw)
In-Reply-To: <20040315034125.GA5295@schmorp.de>
Hi!
> > '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).
Hmm, is there way to force raid5 to check parity?
Mostly "degraded" mode with all disks online. Could be
usefull for cabling problems and debugging raid...
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2004-03-25 14:24 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
2004-03-18 7:25 ` Pavel Machek [this message]
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=20040318072521.GB597@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--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
all inboxes | Powered by JetHome®