Ok, it looks like the following recipe can be used to fsck an lvm
snapshot of an ext3 fs with an external journal:
# lvcreate --snapshot /dev/group-a/ums -n ums-snap -L 1G
Logical volume "ums-snap" created
# tune2fs -U time /dev/group-a/ums-snap
tune2fs 1.41.12 (17-May-2010)
# tune2fs -O ^has_journal /dev/group-a/ums-snap
tune2fs 1.41.12 (17-May-2010)
Filesystem's UUID not found on journal device.
Journal removed
# fsck -y -f /dev/group-a/ums-snap
fsck from util-linux-ng 2.16.2
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/ums: 15166/2097152 files (3.7% non-contiguous), 183629/8388608 blocks
If the "tune2fs -U time" step is omitted then the journal device will be
corrupted.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
