Hi,
On Fri, May 12, 2000 at 07:34:17AM +1200, Chris Wedgwood wrote:
> Journalling doesn't completely negate the need for running fsck from
> time to time -- it just ensures the metadata is in what the kernel
> thinks is apparently a reasonable state.
>
> If the kernel goes nuts and craps all over the filesystem, or perhaps
> if some application does something evil, you will still need to
> fsck...
Yes and no. Applications should not be able to cause any damage that
journaling can't recover from, unless your app is actually writing to
the block device directly.
However, if you _do_ have something which is messing your disk, then
the fact that you need to run fsck is the least of your worries. Yes,
kernel metadata may have been stomped on. However, so might user data.
If you have a situation which journaling can't recover from, then in
many cases fsck is not what you want to do --- you want to mkfs and
restore from backup, because your data is no longer trustable.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:25 EST