All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Radovanovici <stefan@nektulos.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvremove won't work
Date: Tue, 09 Jun 2009 12:25:10 +0200	[thread overview]
Message-ID: <4A2E3886.2000604@nektulos.de> (raw)
In-Reply-To: <1244540783.18101.184.camel@breeves.fab.redhat.com>


On 6/9/2009 11:46 AM, Bryn M. Reeves wrote:

> Use dmsetup:
> 
> $ dmsetup info --maj 252 --min 1
> 
> (the output above shows dm is using 252 as its major number for this
> device on your system).
> 
> At a guess it looks like you somehow removed the PV from the VG while a
> logical volume was mapped on it.

First of all, thanks for the info. I am not a LVM expert and this is useful information. dmsetup shows this:

root@neriak:/sys/block/sda/sda4/holders/dm-1# dmsetup info --maj 252 --min 1
Name:              storage-pvmove0
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        0
Event number:      1
Major, minor:      252, 1
Number of targets: 1
UUID: LVM-SS2wO5K12BwSo1iceXVSiTaYPQzdgEuUoOPgGYKKRLO109x4837eAHZeiSmzzEqW

I think I somehow messed up while trying to get rid of /dev/sda4. I used a GUI for this not the CLI, first I tried to move the extents to other PVs (which I think is that pvmove does) and then to actually remove it from the group (which is probably what vgreduce does). If I am not mistaken, the first operation gave an error even though it appeared to have worked somehow at the time.

Any way I can fix this ?

Thanks,
Stefan

  reply	other threads:[~2009-06-09 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09  6:39 [linux-lvm] pvremove won't work Stefan Radovanovici
2009-06-09  6:54 ` Luca Berra
2009-06-09  7:04   ` Stefan Radovanovici
2009-06-09  9:46     ` Bryn M. Reeves
2009-06-09 10:25       ` Stefan Radovanovici [this message]
2009-06-10  5:38         ` Luca Berra
2009-06-10  5:48           ` Stefan Radovanovici

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=4A2E3886.2000604@nektulos.de \
    --to=stefan@nektulos.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 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.