fsck and system crashes
William Anderson
ubuntu.lists at zensoft.net
Wed Oct 20 09:51:22 UTC 2004
Daniel Robitaille wrote:
>>It's called journaling filesystem. Mandrake should also use one by
>>default. Shouldn't be any reason to run fsck unless something REALLY
>>bad has happened.
>
> actually noticed the other day that Ubuntu did do a fsck after my 30th reboot.
> On my 30gb it didn't take that long so I didn't really care, and
> actually think it would be a good idea to do automatically after a
> unclean shutdown just to be on the safe side of things.
# tune2fs -c 0 -i 0
should sort that out - sets the maximum mount count and interval between
checks to zero (off) for automatic fscking.
Note that the man page states:
"It is strongly recommended that either -c (mount-count-dependent) or -i
(time-dependent) checking be enabled to force periodic full e2fsck(8)
checking of the filesystem. Failure to do so may lead to filesystem
corruption due to bad disks, cables, memory, or kernel bugs to go unnoticed
until they cause data loss or corruption."
--
_ __/| William Anderson | Brodie: The Force is strong with this one
\`O_o' neuro at well dot com | Jay: Dude, don't encourage him
=(_ _)= http://neuro.me.uk/ | -- Mallrats, (1995)
U - Thhbt! GPG 0xFA5F1100 |
More information about the ubuntu-users
mailing list