From: Otto Wyss <otto.wyss@bluewin.ch>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: How errorproof is ext2 fs?
Date: Fri, 14 Sep 2001 21:16:53 +0200 [thread overview]
Message-ID: <3BA257A5.E74DDBAB@bluewin.ch> (raw)
In-Reply-To: <E15hebh-0007QK-00@the-village.bc.nu>
> > This leaves me a bad taste of Linux in my mouth. Does ext2 fs really behave so
> > worse in case of a crash? Okay Linux does not crash that often as MacOS does, so
>
> That sounds like it behaved well. fsck didnt have enough info to safely
> do all the fixup without asking you. Its not a reliability issue as such.
>
Well it could also be the fact that almost no activity was going on on both
systems.
> > it does not need a good error proof fs. Still can't ext2 be made a little more
> > error proof?
>
> Ext3 is a journalled ext2. Its in the 2.4-ac kernel trees. Reiserfs in the
> -ac tree also supports big endian boxes.
>
At least ext2 and probably all the journalling fs lacks a feature the HFS+ from
the Mac has (bad tongues might say "needs"), to keep open files without activity
in a state where a crash has no effect. I don't know how it is done since I'm no
fs expert but my experience with my Mac (resetting about once a month without
loosing anything) shows that it's possible.
I'd rather like to see this feature appear in one fs for Linux (preferable
ext2). I think it's always better to not have error instead of fixing them afterwards.
O. Wyss
next prev parent reply other threads:[~2001-09-14 19:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 21:30 How errorproof is ext2 fs? Otto Wyss
2001-09-13 21:53 ` Joel Jaeggli
2001-09-13 22:05 ` Alan Cox
2001-09-14 19:16 ` Otto Wyss [this message]
2001-09-14 20:39 ` Mike Fedyk
2001-09-16 8:58 ` Rogier Wolff
2001-09-16 10:00 ` Frank Schneider
2001-09-16 10:14 ` Luigi Genoni
[not found] ` <3BA1E670.9010300@foogod.com>
2001-09-14 20:37 ` Otto Wyss
2001-09-14 23:09 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-09-14 13:09 Jesse Pollard
[not found] <Pine.LNX.4.10.10109140953100.24181-100000@coffee.psychology.mcmaster.ca>
2001-09-14 20:47 ` Otto Wyss
2001-09-14 21:38 ` Andreas Dilger
2001-09-15 6:39 Timothy A. Seufert
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=3BA257A5.E74DDBAB@bluewin.ch \
--to=otto.wyss@bluewin.ch \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.