From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: otto.wyss@bluewin.ch, linux-kernel@vger.kernel.org
Subject: Re: How errorproof is ext2 fs?
Date: Sun, 16 Sep 2001 10:58:46 +0200 (MEST) [thread overview]
Message-ID: <200109160858.KAA28624@cave.bitwizard.nl> (raw)
In-Reply-To: <E15hebh-0007QK-00@the-village.bc.nu> from Alan Cox at "Sep 13, 2001 11:05:13 pm"
Alan Cox wrote:
> > due to an not responding USB-keyboard/-mouse (what a nice coincident). Now while
> > the Mac restarted without any fuse I had to fix the ext2-fs manually for about
> > 15 min. Luckily it seems I haven't lost anything on both system.
> >
> > 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, fsck wants to ask
"Found an unattached inode, connect to lost+found?"
to the user and will interrupt an automatic reboot for that.
This is bad: The safe choice is safe: It won't cause data-loss.
Maybe it should report it (say by Email), but interrupting a reboot
just for connecting a couple of files to lost+found, that's
rediculous.
If it would give me enough information when I do this manually, I'd
make an informed decision. However, what are the chances of me knowing
that inode 123456 is a staroffice bak-file? So the only way to safely
operate is to link them into lost+found, and then to look at the files
manually.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
next prev parent reply other threads:[~2001-09-16 8:59 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
2001-09-14 20:39 ` Mike Fedyk
2001-09-16 8:58 ` Rogier Wolff [this message]
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=200109160858.KAA28624@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=otto.wyss@bluewin.ch \
/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.