Re: Ext3fs and fsck
Paolo Falcone <fallenlordx@edsamail.com.ph> writes:
>>blaubaer:~# e2fsck /dev/hdb1
>>e2fsck 1.25 (20-Sep-2001)
>>/dev/hdb1 is mounted.
>>WARNING!!! Running e2fsck on a mounted filesystem may cause
>>SEVERE filesystem damage.
>
> This is default behavior. But you need to delete the journal
> file first, else you wreck your ext3fs partition, before committing
> to fsck.
No, e2fsck works fine on ext3 partitions. It just doesn't want to
work on mounted partitions. Remount root as read-only (mount / -o
ro,remount) and try it again.
> The second one is to tweak your ext3fs partition. issue:
>
> tune2fs -c0 -i0 /dev/hdb1
Bad idea. From the tune2fs man page
You should strongly consider the consequences of
disabling mount-count-dependent checking entirely.
Bad disk drives, cables, memory, and kernel bugs
could all corrupt a filesystem without marking the
filesystem dirty or in error. If you are using
journaling on your filesystem, your filesystem will
never be marked dirty, so it will not normally be
checked. A filesystem error detected by the kernel
will still force an fsck on the next reboot, but it
may already be too late to prevent data loss at
that point.
and
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.
> You won't really need fsck unless you screw up big time (playing
> around as root most of the time does that...).
Untrue.
--
Alan Shutko <ats@acm.org> - In a variety of flavors!
Anger kills as surely as the other vices.
Reply to: