From: Pavel Machek <pavel@suse.cz>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Murphy hits (Kernel 2.6, ext2, "check=strict"): corrupted filesystem
Date: Tue, 13 Jul 2004 22:48:33 +0200 [thread overview]
Message-ID: <20040713204833.GI3654@openzaurus.ucw.cz> (raw)
In-Reply-To: <40F251F1.1057.35E0C3@rkdvmks1.ngate.uni-regensburg.de>
Hi!
> I'd like to present a little story how to shredder your ext2 filesystem:
>
> I was installing SuSE Linux 9.1 when the kernel froze rather late during
> installation. So I had to reset the PC. There is a minor bug in the forementioned
You call this "minor"?
> Why I'm writing this: If something can go wrong, eventually it will. For a true
> disaster you always need more than just one problem (1: Kernel freeze, 2: no fsck
> being run, 3: kernel happily mounts unclean filesystem for read-write).
3 is feature. It prints warning, but lets you mount it. I sometimes mount
broken fs's rw; it actually saved me once when I was hitting fsck bug.
It is also handy when quickly recovering scratch machine.
MS-DOS had no fsck... and survive. ext2 can survive with similar results
if you just dont fsck...
> I think nobody really wants to read reports where Linux has shreddered a
> filesystem, do we?
I actually liked your report ;-).
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2004-07-13 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 6:55 Murphy hits (Kernel 2.6, ext2, "check=strict"): corrupted filesystem Ulrich Windl
2004-07-13 20:48 ` Pavel Machek [this message]
2004-07-14 6:24 ` Ulrich Windl
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=20040713204833.GI3654@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--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.