swsusp is at it... again

From: Pavel Machek (pavel@ucw.cz)
Date: Mon Mar 04 2002 - 18:06:24 EST

Next message: Pavel Machek: "Re: Lucent WinModem"
Previous message: Pavel Machek: "swsusp for 2.4.18 (23)"
Next in thread: fchabaud@free.fr: "Re: swsusp is at it... again"
Reply: fchabaud@free.fr: "Re: swsusp is at it... again"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi!

After about 20 resume cycles (compiled kernel with swsusp making
machine suspend/resume) I got that nasty FS corruption, again.

So...

1) Maybe your ext3 patches are not at fault.

2) Be carefull using swsusp patch. Real carefull.

3) Don't trust fsck. At this kind of corruption, e2fsck 1.19 will
report "clean" but will not repair it, putting your fs into
self-destruct mode. Bad bad. Its fixed on new versions. Always run
fsck twice, second time with -f.
Pavel

-- 
(about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
-
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/

Next message: Pavel Machek: "Re: Lucent WinModem"
Previous message: Pavel Machek: "swsusp for 2.4.18 (23)"
Next in thread: fchabaud@free.fr: "Re: swsusp is at it... again"
Reply: fchabaud@free.fr: "Re: swsusp is at it... again"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Mar 07 2002 - 21:00:36 EST