linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Hannes Dorbath <light@theendofthetunnel.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Where to report bugs?
Date: Wed, 03 Oct 2007 20:31:28 +0200	[thread overview]
Message-ID: <4703E000.4050307@theendofthetunnel.de> (raw)
In-Reply-To: <20071003171552.GL18444@agk.fab.redhat.com>

Alasdair G Kergon wrote:
> If you want to use bugzilla rather than this mailing list, file bugs that
> you find in upstream CVS against:
> 
>   Product Fedora
>   Version devel
>   Component lvm2

OK, if this ML is fine as well, I'll post it here:

Summary is that an active snapshot LV that loses its COW PV and is in
the same VG as the origin LV makes the origin LV disappear.

Example:
1. Create 2 PVs. Let's say /dev/sda and /dev/sdb
2. Create a VG with PV /dev/sda named data
3. Create a LV on VG data named origin
4. Extend VG data with PV /dev/sdb
5. Create a snapshot LV of LV origin, in VG data, on PV /dev/sdb, named snap
6. Remove /dev/sdb physically from the system (or disable in BIOS)
7. Reboot
8. Use vgreduce --removemissing to get VG data up again

LV origin is gone and can only be brought back from backup with
vgcfgrestore.

lvm 2.02.28
dev-mapper 1.02.22-r1
kernel 2.6.22-r8


-- 
Best regards,
Hannes Dorbath

  reply	other threads:[~2007-10-03 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 15:18 [linux-lvm] Where to report bugs? Hannes Dorbath
2007-10-03 17:15 ` Alasdair G Kergon
2007-10-03 18:31   ` Hannes Dorbath [this message]
2007-10-03 19:18     ` 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=4703E000.4050307@theendofthetunnel.de \
    --to=light@theendofthetunnel.de \
    --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).