I've just been testing 2.4.15 on my NetWinder (which was running 2.4.15-pre5
quite happily - its built several kernels and been through a fair number of
reboot cycles with that version).
With 2.4.15, I can now 100% reproduce every time filesystem corruption of
an ext2 filesystem, specifically in /var/lock/subsys/.
/var/lock/subsys contains a load of 0 byte files, one for each daemon that
is started by the redhat-like boot scripts. On shutdown they're removed.
After a second boot with 2.4.15, all the names are still present in the
directory, rm complains with:
rm: cannot remove `/var/lock/subsys/xyz': Input/output error
stracing rm reveals that lstat of a file in /var/lock/subsys/ returns -EIO.
Trying to get a directory listing results in every single file giving an
input/output error.
This is just a heads up - several people are already looking into it.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
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/