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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Sep 23 2001 - 21:00:13 EST