[linux-lvm] How do you mount a snapshot?

Chris Mason mason at suse.com
Mon Dec 11 14:58:18 UTC 2000


On Sunday, December 10, 2000 22:48:08 -0800 David Gould <dg at suse.com> wrote:

> On Fri, Dec 08, 2000 at 09:30:50PM +0100, Christian Limpach wrote:
>> > Ok, so we are agreeing, it does not work on ext2 either unless you sync
>> > and do not write between the sync and the snapshot. Doable, but not
>> exactly
>> > "safe".
>> 
>> hmm, I think it works for ext2 because you can always mount an ext2
>> filesystem even if it's in an inconsistent state.  This is what happens
>> everytime when your machine panics and you need to fsck your disks during
>> the reboot, the root filesystem is mounted read-only...  It's my
> 
> Ok, but then you have an inconsistant filesystem. Which is not exactly
> what I think of as "works" or "safe". My point was that snapshots are
> great, but don't make the problem of consistancy magically disappear.
> 

Yes.  With ext2, the admin can take steps to make his FS consistent during
the snapshot.  It would be a painful manual process, but it is at least
possible.

It would not be useful for snapshots to allow reiserfs disks to be mounted
without a journal replay though.  An inconsistent ext2 FS might have a few
directories screwed up, or a rename in progress, or some bad bitmaps  (or
much worse, but we are pretending things are normal here).  But, most of
the time it will be mostly valid.

reiserfs just has one btree for everything, so if the snapshot comes in the
middle of a given operation, it affects the btree for the whole FS.  This
means an inconsistent reiserfs disk has a much higher chance of having
serious problems, almost regardless of the type of operation that was going
on.  So, the snapshot API does two things.  It waits for all transaction
operations to finish, and then it blocks new ones until the snapshot is
setup.

Christian, just let me know if that doesn't answer your question.

-chris




More information about the linux-lvm mailing list