| To: | Al Boldi <a1426z@xxxxxxxxx> |
|---|---|
| Subject: | Re: Good, recent FS comparison? |
| From: | Jamie Lokier <jamie@xxxxxxxxxxxxx> |
| Date: | Thu, 22 Sep 2005 13:14:23 +0100 |
| Cc: | linux-fsdevel@xxxxxxxxxxxxxxx, Linux RAID Mailing List <linux-raid@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <200509220034.42284.a1426z@gawab.com> |
| References: | <6d5bedd8050915131148b8108a@mail.gmail.com> <200509162258.37730.a1426z@gawab.com> <20050921153703.GB19896@mail.shareable.org> <200509220034.42284.a1426z@gawab.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | SV: XFS on 6TB systems, Thor Eivind Brantzeg |
|---|---|
| Next by Date: | Re: howto preallocate to minimize fragmentation, Eric Sandeen |
| Previous by Thread: | Re: Good, recent FS comparison?, Al Boldi |
| Next by Thread: | XFS filesystem died Looking for Help, AndyLiebman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |