From: Rik Herrin <rikherrin@yahoo.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM2 Snapshots Question
Date: Sun, 22 Oct 2006 04:06:59 -0700 (PDT) [thread overview]
Message-ID: <20061022110659.82422.qmail@web52911.mail.yahoo.com> (raw)
Hi,
I had a question regarding LVM2 snapshots. I read the following about snapshots (taken from
http://www.tldp.org/HOWTO/LVM-HOWTO/snapshotintro.html):
"This facility does require that the snapshot be made at a time when the data on the logical volume is in a consistent state - the VFS-lock patch for LVM1 makes sure that some filesystems do this automatically when a snapshot is created, and many of the filesystems in the 2.6 kernel do this automatically when a snapshot is created without patching."
Does this mean that I don't have to unmount (or remount ro) a partition if I'm using a 2.6 kernel to take a snapshot and I can rest assured that the logical volume will be in a consistent state? Thanks for your help.
next reply other threads:[~2006-10-22 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 11:06 Rik Herrin [this message]
2006-10-22 11:12 ` [linux-lvm] LVM2 Snapshots Question Alasdair G Kergon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061022110659.82422.qmail@web52911.mail.yahoo.com \
--to=rikherrin@yahoo.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).