From: Jamie Lokier <jamie@shareable.org>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-fsdevel@vger.kernel.org,
Linux RAID Mailing List <linux-raid@vger.kernel.org>,
linux-xfs@oss.sgi.com
Subject: Re: Good, recent FS comparison?
Date: Thu, 22 Sep 2005 13:14:23 +0100 [thread overview]
Message-ID: <20050922121423.GA30182@mail.shareable.org> (raw)
In-Reply-To: <200509220034.42284.a1426z@gawab.com>
Al Boldi wrote:
> Jamie Lokier wrote:
> > Al Boldi wrote:
> > > ext3 is rock-solid!
> >
> > If only. Recently I had a system come up after a power cycle with a
> > directory where reading any file in that directory gives an I/O error.
> > The disk is fine, and it's using ext3 in ordered mode, with IDE
> > write-caching disabled to be sure.
>
> 2.4 or 2.6?
>
> In 2.4 try a reboot and force an fsck before mounting.
2.4.26, uclinux - it's an embedded device.
Doing an fsck before mounting would be an unacceptable boot-time delay.
Why do you suggest that, specifically for 2.4? Is there a known
problem with 2.4 and ext3?
Thanks,
-- Jamie
next prev parent reply other threads:[~2005-09-22 12:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6d5bedd8050915131148b8108a@mail.gmail.com>
[not found] ` <432A37BF.7060305@dtbb.net>
2005-09-16 21:17 ` Good, recent FS comparison? Al Boldi
2005-09-18 9:15 ` Tyler
2005-09-18 11:29 ` Raz Ben-Jehuda(caro)
2005-09-18 12:32 ` Al Boldi
2005-09-18 16:34 ` Matt Stegman
2005-09-20 21:00 ` George N. White III
2005-12-27 23:33 ` James Northrup
2005-12-28 1:45 ` Randy.Dunlap
2005-12-28 2:02 ` James Northrup
2005-09-21 15:37 ` Jamie Lokier
2005-09-21 21:34 ` Al Boldi
2005-09-22 12:14 ` Jamie Lokier [this message]
2005-09-22 13:55 ` Al Boldi
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=20050922121423.GA30182@mail.shareable.org \
--to=jamie@shareable.org \
--cc=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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 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).