Package: e2fsprogs
Version: 1.41.12-2
Severity: normal
On a lvm2 based system I have an ext3 fileystem with an external journal.
I want to use lvm2s snapshot facilities to do online backups and fscks.
So I create a snapshot of my filesystem.
Problem #1 - if I try to fsck the snapshot it proposes that I rerun the
journal, even suggesting that the journal be cleared.
# fsck -v -f /dev/group-a/ums-snap
fsck from util-linux-ng 2.16.2
e2fsck 1.41.12 (17-May-2010)
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? no
Clear journal<y>? no
If I do rerun the journal the snapshot is, of course, corrupted. I
imagine that if I clear the journal the filesystem will be damaged.
Problem #2 - if, to avoid problem #1 I remove the journal from the
snapshot with tune2fs:
# tune2fs -O ^has_journal /dev/group-a/ums-snap
tune2fs 1.41.12 (17-May-2010)
Journal removed
It destroys the journal of the mounted volume - when I next mount the
volume it complains that it can't find the journal(*)
(* In fact it says: EXT3-fs: External journal has more than one user
(unsupported) but I'm guessing that it's the message that's wrong).
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-3-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages e2fsprogs depends on:
ii e2fslibs 1.41.12-2 ext2/ext3/ext4 file system librari
ii libblkid1 2.17.2-2 block device id library
ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib
ii libcomerr2 1.41.12-1 common error description library
ii libss2 1.41.12-1 command-line interface parsing lib
ii libuuid1 2.16.2-0 Universally Unique ID library
ii util-linux 2.16.2-0 Miscellaneous system utilities
e2fsprogs recommends no packages.
Versions of packages e2fsprogs suggests:
pn e2fsck-static <none> (no description available)
pn gpart <none> (no description available)
pn parted <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
