From: Bas Mevissen <ml@basmevissen.nl>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Jan Dittmer <j.dittmer@portrix.net>,
linux-kernel@vger.kernel.org
Subject: Re: ext3 on raid5 failure
Date: Thu, 19 Feb 2004 10:27:58 +0100 [thread overview]
Message-ID: <4034819E.7030004@basmevissen.nl> (raw)
In-Reply-To: <4032D6E6.1060906@tmr.com>
Bill Davidsen wrote:
>
>> It looks like this only appeared once. The FS looks fine now. So I guess
>> I won't be able to reproduce it. Let's just go to 2.6.[23] and see if
>> it happens again.
>
> Did this go away on reboot, or did you have to fix it? If it went away
> on reboot, it could be that the copy of the inode in memory was borked.
>
I really had to fix it. But, it never appeared again until now. So maybe
this was just caused by some crash while experimenting with swsusp2.
Regards,
Bas.
next prev parent reply other threads:[~2004-02-19 9:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 10:27 ext3 on raid5 failure Jan Dittmer
2004-01-18 18:02 ` Mike Fedyk
2004-01-19 15:30 ` Theodore Ts'o
2004-01-23 8:22 ` Jan Dittmer
2004-01-27 19:08 ` Theodore Ts'o
2004-01-28 10:54 ` Jan Dittmer
2004-01-29 11:44 ` Theodore Ts'o
2004-02-04 9:24 ` Bas Mevissen
2004-02-04 9:43 ` Nigel Cunningham
2004-02-04 11:38 ` Bas Mevissen
2004-02-04 20:49 ` Nigel Cunningham
2004-02-17 23:14 ` Pavel Machek
2004-02-17 23:58 ` Kiko Piris
2004-02-06 19:18 ` Theodore Ts'o
2004-02-09 8:55 ` Bas Mevissen
2004-02-18 3:07 ` Bill Davidsen
2004-02-19 9:27 ` Bas Mevissen [this message]
2004-02-19 19:47 ` Bill Davidsen
2004-01-28 11:06 ` Jan Dittmer
2004-02-19 2:32 ` Leandro Guimarães Faria Corsetti Dutra
2004-02-19 8:07 ` Jan Dittmer
2004-02-19 13:50 ` Leandro Guimarães Faria Corcete Dutra
2004-02-19 14:58 ` Leandro Guimarães Faria Corsetti Dutra
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 17:45 Muhammad L.
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=4034819E.7030004@basmevissen.nl \
--to=ml@basmevissen.nl \
--cc=davidsen@tmr.com \
--cc=j.dittmer@portrix.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.