[Bug 31730] Re: JFS is flakey
floid
jkanowitz at snet.net
Wed Apr 12 19:04:21 UTC 2006
With 2.6.15-20 i386 (32-bit), Dapper Flight 6, JFS is giving equal headaches.
The biggest showstopper appears to be that fsck.jfs does not always detect a dirty filesystem, leading to a 'successful' journal replay in ignorance of corrupt entries. This is being a particular bear with X.org/gdm-related entries in /tmp, given my machine's tendency to jam itself in odd ways immediately after opening files there. (See #39333)
Doing a forced check actually cleans things up.
A concomitant issue is the boot process's handling of the case where fsck.jfs doesn't do its job and so a JFS root partition comes up read-only. Lots of things fail there, obviously, but some truly weird things happen (bash with no job control coming up 'over' a text-gui gdm complaint dialog, other consoles and instances of login seeming to initialize or not at random) ...
IMHO, the boot scripts should check that all requisite locations are writable (/tmp, /var/log, where else?) and bomb straight to a shell -- with instructions for continuing after a manual fsck -- if not.
--
JFS is flakey
https://launchpad.net/malone/bugs/31730
More information about the kernel-bugs
mailing list