https://bugzilla.novell.com/show_bug.cgi?id=310483 Ruediger Oertel <ro@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ro@novell.com |mkoenig@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=310483 User Eduard.Avetisyan@desy.de added comment https://bugzilla.novell.com/show_bug.cgi?id=310483#c2 Eduard Avetisyan <Eduard.Avetisyan@desy.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Eduard.Avetisyan@desy.de Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #2 from Eduard Avetisyan <Eduard.Avetisyan@desy.de> 2008-11-22 16:14:55 MST --- Sorry, I disagree with you, Matthias. The forced check was necessary for ext2, for ext3 it's not anymore. I know one can adjust the check time manually, but I think fsck has to be patched to allow some kind of timer, like 3-5 seconds, and do the actual forced check only if no key is pressed. The point is that with 2 new opensuse versions per year many people reinstall way to often and all the filesystem tunings are overwritten. next, many people use opensuse on laptops, and this unwanted fsck's turn on most inconvenient moment leaking your battery, and there's no way to stop it. It's going to get worse with time since HDDs tend to grow larger... I would like to reopen the bug, or rather a feature request. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=310483 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=310483#c3 Matthias Koenig <mkoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FEATURE --- Comment #3 from Matthias Koenig <mkoenig@novell.com> 2009-02-11 08:56:16 MST --- According to http://lwn.net/Articles/248180/ fsck's are not obsolete even for journalling filesystems:

...

Some file system developers initially took this to mean that no fsck was needed at all. In part, this was true - the system no longer needed to repair half-finished writes by scanning the entire file system, it only had to replay the log. But fixing half-finished writes was only one part of what fsck did. It also checked for and repaired corruption caused by disk errors, file system bugs, administrator error, and any other source. These sources of errors are less common and can be ignored in development, but become a major problem in production use. Nobody wanted to repair a journaling file system by hand any more than any other file system. fsck in the sense of "repair half-completed writes" is unnecessary for journaling file systems (or copy-on-write file systems) but it is still necessary in the sense of "check for and repair file system corruption when something unexpected goes wrong." <<

Anyway this is not a bug and if you want to discuss changes in this area please open a request in openfate: https://features.opensuse.org/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.