Re: Murphy hits (Kernel 2.6, ext2, "check=strict"): corrupted filesystem
From: Ulrich Windl (Ulrich.Windl_at_rz.uni-regensburg.de)
Date: 07/14/04
- Previous message: Roy Butler: "Re: kconfig's file handling (was: XFS: how to NOT null files on fsck?)"
- In reply to: Pavel Machek: "Re: Murphy hits (Kernel 2.6, ext2, "check=strict"): corrupted filesystem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Pavel Machek <pavel@suse.cz> Date: Wed, 14 Jul 2004 08:24:56 +0200
On 13 Jul 2004 at 22:48, Pavel Machek wrote:
> 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"?
...in the eyes of real-life (Linux distributor's) software support it is. Not in
mine.
>
> > 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...
The syslog was full with attempts to access the device outside its limits. Seems
there was some bad constellation after the kernel crash.
>
> > I think nobody really wants to read reports where Linux has shreddered a
> > filesystem, do we?
>
> I actually liked your report ;-).
(after two days of work and reinstalling about 90% of the RPMs I have a working
system again. The other stupid thing that doesn't belong to this list is: RPM v4
fails to install a package if one of the packet's file targets exists as a
directory (happened after the crash and fsck to me). RPM then seems unable to
cleanup and leaves aditional files with a semicolon and hexadecimal number as
suffix then. Repeated invocations create new files then...)
Regards,
Ulrich
(& thanks for replying)
-
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/
- Previous message: Roy Butler: "Re: kconfig's file handling (was: XFS: how to NOT null files on fsck?)"
- In reply to: Pavel Machek: "Re: Murphy hits (Kernel 2.6, ext2, "check=strict"): corrupted filesystem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
