Skip to contentSkip to conversation

New concept of ext3 disk checks

DISCUSSION Andi Kleen 2 participants 2 messages Aug 12, 2004 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#2 lore raw
Quoted 4 lines · Theodore Ts'o

4) If there were no errors detecting by the fsck run, run the command "tune2fs -C 0 -T now /dev/XXX" on the live filesystem. This sets the mount count and last filesystem checked time to the appropriate values in the superblock.

Is it safe now to run tune2fs on a mounted busy fs? afaik it would need at least support to quiescence the fs temporarily. Otherwise you have a race window where changes to the superblock could get lost.

-Andi

#3 lore raw
Quoted 10 lines · Andi Kleen
Quoted 4 lines · Theodore Ts'o

4) If there were no errors detecting by the fsck run, run the command "tune2fs -C 0 -T now /dev/XXX" on the live filesystem. This sets the mount count and last filesystem checked time to the appropriate values in the superblock.

Is it safe now to run tune2fs on a mounted busy fs? afaik it would need at least support to quiescence the fs temporarily. Otherwise you have a race window where changes to the superblock could get lost.

Modern versions of e2fsprogs do byte-level writes only to the fields that are being changed by the userspace program; given that these are fields that are not touched by the kernel once the filesystem is mounted, this is safe.

- Ted