public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: otto.wyss@bluewin.ch, linux-kernel@vger.kernel.org
Subject: Re: How errorproof is ext2 fs?
Date: Fri, 14 Sep 2001 08:09:04 -0500 (CDT)	[thread overview]
Message-ID: <200109141309.IAA86711@tomcat.admin.navo.hpc.mil> (raw)

Otto Wyss <otto.wyss@bluewin.ch>:
> While reading the thread about "HFS Plus on Linux?" at
> "debian-powerpc@list.debian.org" I had the following experience:
> 
> Within an hour I had to hard reset both of my computers, first my Linux-i386 due
> to a complete lockup of the system while using el3diag, second my MacOS-powermac
> 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
> it does not need a good  error proof fs. Still can't ext2 be made a little more
> error proof?
> 
> Okay, there are other fs for Linux which cope better with such a situation, but
> are they really more errorproof or are they just better in fixing up the mess
> afterwards? Could there be more attention in not creating errors instead of
> fixing them afterwards?

I've used linux for about 8 years now. The only time I've had a catastrophic
failure was with a disk drive went south.

About the only times I've seen ext2fs require manual repair is a crash/power
failure during fsck on boot. It doesn't happen very often. Even then, it
may not be a serious falure, just the type of error that requires a choice
in fix - missing inode/partially written inode in the root file system will
usually require the choice of deleting, or putting in lost+found.

No file system is immune to that level of failure. Some are better at
hiding the damage (xfs will lose free data blocks like mad - 3 in a row lost
6GB out of 12, though no used data was (visibly) lost.

15 minutes isn't that bad - wait until you have to spend 30 minutes to
3 hours on an NTFS or FAT32 rebuild, only to find you have to reinstall.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

             reply	other threads:[~2001-09-14 13:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-14 13:09 Jesse Pollard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-15  6:39 How errorproof is ext2 fs? Timothy A. Seufert
     [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-13 21:30 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
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

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=200109141309.IAA86711@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox