> After reboot fsck was NOT run, so it is possible that there
> might be some corruption - but I ran fsck on my non-root partition
> after boot, and it did not show any problems.
fsck -f
Filesystem _is_ marked clean, so unless you do forced fsck no checks
are done.
Moreover, attempt to work with corrupted fs can break in very interesting
ways, so unless you do fsck -f even correct kernel (be it patched 2.4.15
or something earlier than 2.4.15-pre9) will not help.
-
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/