> On Jul 17, 2002 13:45 +0200, Matthias Andree wrote:
> > On Tue, 16 Jul 2002, Shawn wrote:
> > > In this case, can you use a RAID mirror or something, then break it?
> > >
> > > Also, there's the LVM snapshot at the block layer someone already
> > > mentioned, which when used with smaller partions is less overhead.
> > > (less FS delta)
> > All these "solutions" don't work out, I cannot remount R/O my partition,
> > and LVM low-level snapshots or breaking a RAID mirror simply won't work
> > out. I would have to remount r/o the partition to get a consistent image
> > in the first place, so the first step must fail already...
> Have you been reading my emails at all? LVM snapshots DO ensure that
> the snapshot filesystem is consistent for journaled filesystems.
What kernel version is necessary to achieve this on production kernels
(i. e. 2.4)?
Does "consistent" mean "fsck proof"?
Here's what I tried, on Linux-2.4.19-pre10-ac3 (IIRC) (ext3fs):
(from memory, history not available, different machine):
lvcreate --snapshot snap /dev/vg0/home
e2fsck -f /dev/vg0/snap
dump -0 ...
It reported zero dtime for one file and two bitmap differences.
Does "consistent" mean "consistent after you replay the log?" If so,
that's still a losing game, because I cannot fsck the snapshot (it's R/O
in the LVM case at least) to replay the journal -- and I don't assume
dump 0.4b29 (which I'm using) goes fishing in the journal, but did not
use the dump source code.
dump did not complain however, and given what e2fsck had to complain,
I'd happily force mount such a file system when just a deletion has not
-- Matthias Andree - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/