From: Gerry Reno <greno@verizon.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] F7 will not boot after running backup w/snapshot
Date: Thu, 01 May 2008 14:15:03 -0400 [thread overview]
Message-ID: <481A08A7.5010305@verizon.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0805011223590.32190@engineering.redhat.com>
Mikulas Patocka wrote:
> ... If you mount the origin device with missing snapshot, you destroy
> the snapshot (even if you don't touch it). The snapshot can no longer
> be repaired.
>
> So it is safer to not activate device in this case then destroy data.
Why? What value is the old snapshot at this point? You just had a system
reboot in the middle of a snapshotted backup so all you need to do is
get the system up, redo another snapshot and retake your backup. I'm not
interested in the old snapshot.
>
> Imagine, for example, you have origin and snapshot, you reconfigure
> disks in some weird way that the snapshot disk is inaccessible, you
> boot, and the system automatically starts without the snapshot. And
> you lose any data that you stored on that snapshot.
What is on the old snapshot at this point is probably indeterminate anyway.
> You can with dmsetup (but it has deadlocks). Maybe someone could write
> non-deadlocky snapshot-managing tool that wouldn't depend on lvm vgs,
> pvs and lvs.
>
> Mikulas
Have not used dmsetup. If it has deadlocks, I don't think I want to use it.
Gerry
next prev parent reply other threads:[~2008-05-01 18:15 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 0:53 [linux-lvm] F7 will not boot after running backup w/snapshot Gerry Reno
2008-04-30 2:29 ` Gerry Reno
2008-04-30 3:51 ` Gerry Reno
2008-04-30 14:00 ` Gerry Reno
2008-04-30 15:09 ` Larry Dickson
2008-04-30 17:23 ` Gerry Reno
2008-04-30 18:19 ` Gerry Reno
2008-04-30 18:28 ` Charles Marcus
2008-04-30 20:24 ` Gerry Reno
2008-04-30 21:19 ` Milan Broz
2008-04-30 22:30 ` Gerry Reno
2008-05-01 15:48 ` malahal
2008-05-01 16:30 ` Mikulas Patocka
2008-05-01 18:15 ` Gerry Reno [this message]
2008-05-01 18:38 ` Charles Marcus
2008-05-01 19:37 ` Gerry Reno
2008-05-01 19:42 ` Charles Marcus
2008-05-01 19:53 ` Gerry Reno
2008-05-01 20:03 ` Charles Marcus
2008-05-01 20:21 ` Gerry Reno
2008-05-01 20:25 ` Alasdair G Kergon
2008-05-01 20:30 ` Gerry Reno
2008-05-01 20:34 ` Charles Marcus
2008-05-01 20:36 ` Gerry Reno
2008-05-01 20:44 ` Charles Marcus
2008-05-01 20:57 ` Gerry Reno
2008-05-01 21:59 ` Alasdair G Kergon
2008-05-01 22:12 ` Gerry Reno
2008-05-01 23:50 ` Gerry Reno
2008-05-02 0:38 ` Stuart D. Gathman
2008-05-02 0:47 ` Stuart D. Gathman
2008-05-02 2:03 ` Gerry Reno
2008-05-02 8:14 ` Marek Podmaka
2008-05-02 14:00 ` Gerry Reno
2008-05-02 14:14 ` Charles Marcus
2008-05-02 14:25 ` Larry Dickson
2008-05-02 14:45 ` Marek Podmaka
2008-05-02 14:38 ` Stuart D. Gathman
2008-05-02 14:47 ` Bryn M. Reeves
2008-05-02 15:05 ` Marek Podmaka
2008-05-02 15:17 ` Stuart D. Gathman
2008-05-02 15:30 ` Gerry Reno
2008-05-02 15:36 ` Bryn M. Reeves
2008-05-03 2:27 ` Mikulas Patocka
2008-05-04 0:45 ` [linux-lvm] Temporary shapshots Stuart D. Gathman
2008-05-05 14:30 ` Larry Dickson
2008-05-05 14:45 ` Charles Marcus
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=481A08A7.5010305@verizon.net \
--to=greno@verizon.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.