linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Tim Connors <tconnors+linuxkernel1070509204@astro.swin.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 future
Date: Thu, 4 Dec 2003 06:41:12 +0100	[thread overview]
Message-ID: <20031204054112.GC11325@alpha.home.local> (raw)
In-Reply-To: <slrn-0.9.7.4-10320-18132-200312041440-tc@hexane.ssi.swin.edu.au>

Hi !

On Thu, Dec 04, 2003 at 02:45:13PM +1100, Tim Connors wrote:
> > What about ext3?  I tend to prefer ext3 since I know how it works more than
> > the others, and it puts data integrity ahead of performance, which is the
> > way things should be (TM).
> 
> Is it true that JFS still doesn't use a /lost+found?
<...>

> I have had plenty of problems with it. One I can think of is under
> debian, after your $RANDOM mounts, it doesn't manage to do the
> automatic forced fsck, so none of the filesystems get mounted. It
> tries to stumble along without having mounted /usr. I have to reboot,
> log in single user, and manually fsck. I don't know whther this is a
> fsck.jfs or a debian deficiency.

I recently had a very bad experience on my notebook with ext3 and fsck. It
had not checked the disk for 180 days, and started it... I can now estimate
about 60 files I lost in /usr (most of them in /usr/bin), but I regularly
discover new missing ones. Since this notebook has experience lots of
crashes, I think that the FS already was in bad situation, but these files
were still OK for me just before I shut it down. I cannot imagine not
noticing a "make: command not found" after a day of compilation. So I
stuffed some missing files in it again and it's OK now. I really don't
know what happened. Perhaps I fscked during a solar flare :-)

Cheers
Willy


  reply	other threads:[~2003-12-04  5:45 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01 14:25 Linux 2.4 future Marcelo Tosatti
2003-12-01 15:04 ` Ian Kent
2003-12-01 15:33   ` Christoph Hellwig
2003-12-01 21:36     ` Peter C. Norton
2003-12-01 23:54       ` Arjan van de Ven
2003-12-02  1:11         ` Ian Kent
2003-12-02 20:13           ` Peter C. Norton
2003-12-02 20:10         ` Peter C. Norton
2003-12-02 20:18           ` Arjan van de Ven
2003-12-02 20:46             ` Peter C. Norton
2003-12-03  1:23               ` Ian Kent
2003-12-03 10:36                 ` Matthias Andree
2003-12-03 14:49                   ` Ian Kent
2003-12-03 15:00                     ` Matthias Andree
2003-12-04  6:24                       ` Ian Kent
2003-12-02 21:56             ` Bryan Whitehead
2003-12-02  8:17       ` Christoph Hellwig
2003-12-02  1:09     ` Ian Kent
2003-12-02  2:23     ` snpe
2003-12-02  6:39       ` Jan-Benedict Glaw
2003-12-02 18:04         ` Linus Torvalds
2003-12-02 18:45           ` Jan-Benedict Glaw
2003-12-02 19:09             ` Linus Torvalds
2003-12-02 19:13               ` Jan-Benedict Glaw
2003-12-02 19:39               ` Gene Heskett
2003-12-02 20:13                 ` Jeff Garzik
2003-12-02 20:32                 ` Stephan von Krawczynski
2003-12-02 21:48                   ` Gene Heskett
2003-12-02 21:56                     ` Linus Torvalds
2003-12-03  2:36                       ` Harald Arnesen
2003-12-03  9:21                     ` Helge Hafting
2003-12-02 19:59           ` snpe
2003-12-02 22:30             ` Mike Fedyk
2003-12-02 22:43               ` Arnaldo Carvalho de Melo
2003-12-03 14:08                 ` snpe
2003-12-03 13:26                   ` Christoph Hellwig
2003-12-02  8:18       ` Christoph Hellwig
2003-12-01 15:26 ` Norberto Bensa
2003-12-01 23:30   ` 2.6 security patches merged? was: " Mike Fedyk
2003-12-02  0:06     ` Chris Wright
2003-12-02  0:58       ` Måns Rullgård
2003-12-02  1:56         ` Chris Wright
2003-12-02 11:55     ` Marcelo Tosatti
2003-12-02  9:00   ` Matthias Andree
2003-12-02 11:54   ` Ionut Georgescu
2003-12-02 12:03     ` Arnaldo Carvalho de Melo
2003-12-02 13:13       ` Ionut Georgescu
2003-12-02 13:38         ` Ed Sweetman
2003-12-02 14:12           ` Arnaldo Carvalho de Melo
2003-12-02 16:01           ` Ionut Georgescu
2003-12-02 16:08             ` Jeff Garzik
2003-12-02 18:20               ` John Bradford
2003-12-02 20:19               ` Ville Herva
2003-12-02 21:40                 ` Chris Wright
2003-12-02 20:09       ` Stephan von Krawczynski
2003-12-02 20:24         ` Arnaldo Carvalho de Melo
2003-12-02 20:45           ` Stephan von Krawczynski
2003-12-02 21:03             ` Arnaldo Carvalho de Melo
     [not found]       ` <Pine.LNX.4.58.0312021402360.17892@moje.vabo.cz>
     [not found]         ` <20031202131512.GU13388@conectiva.com.br>
     [not found]           ` <Pine.LNX.4.58.0312021433360.8417@moje.vabo.cz>
     [not found]             ` <20031202135423.GB13388@conectiva.com.br>
2003-12-02 20:21               ` Tomas Konir
2003-12-02 18:53                 ` Mike Fedyk
2003-12-02 19:06                   ` Valdis.Kletnieks
2003-12-02 23:13                 ` Jose Luis Domingo Lopez
2003-12-03 18:22                 ` bill davidsen
2003-12-04  1:24                   ` jw schultz
2003-12-04  1:47                     ` Mike Fedyk
2003-12-04  3:45                       ` Tim Connors
2003-12-04  5:41                         ` Willy Tarreau [this message]
2003-12-05  0:14                       ` jw schultz
2003-12-01 15:56 ` Marcelo Tosatti
2003-12-01 21:02 ` David S. Miller
2003-12-03 21:26 ` Jan Rychter
2003-12-03 20:51   ` Jeff Garzik
2003-12-03 21:14   ` Willy Tarreau
2003-12-05 15:33   ` John Jasen
2003-12-05 22:23     ` Mike Fedyk
2003-12-06 15:49     ` Max Valdez

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=20031204054112.GC11325@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tconnors+linuxkernel1070509204@astro.swin.edu.au \
    /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).