From: Tom Diehl <tdiehl@rogueind.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM snapshot?
Date: Sun, 21 Dec 2008 09:33:28 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0812210927010.3626@tigger.tntechs.com> (raw)
Hi,
I have a machine that is running EL5 with xen. One of the DOMU's has an LV
from DOM0 mounted on it to allow access to the data. Is it safe to do
a snapshot of the LV from DOM0 while it is still mounted rw on the DOMU?
What I would like to do is snapshot the LV, fsck the snapshot and if it comes
up clean, continue on. If it shows errors, then I will schedule downtime
for a real fsck.
Does this sound safe or am I going to get into trouble if I do that?
Regards,
--
Tom Diehl tdiehl@rogueind.com Spamtrap address mtd123@rogueind.com
next reply other threads:[~2008-12-21 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 14:33 Tom Diehl [this message]
2008-12-21 18:34 ` [linux-lvm] LVM snapshot? Tim Post
2008-12-23 0:15 ` [linux-lvm] LVM2 robustness w/ large (>100TB) name spaces? Steve Costaras
2008-12-23 1:24 ` Alasdair G Kergon
2008-12-23 1:33 ` Steve Costaras
2008-12-23 10:27 ` Marek Podmaka
2008-12-29 3:06 ` Steve Costaras
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=alpine.LFD.2.00.0812210927010.3626@tigger.tntechs.com \
--to=tdiehl@rogueind.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