All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ossmann <mike@ossmann.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvm2 vgchange -a n problem
Date: Wed Mar 10 16:14:07 2004	[thread overview]
Message-ID: <20040309234328.GA6481@ossmann.com> (raw)
In-Reply-To: <20040308093919.GI4872@reti>

On Mon, Mar 08, 2004 at 09:39:19AM +0000, Joe Thornber wrote:
> 
> i) do a 'dmsetup info <dev>' and confirm that the 'open count' is 0

# dmsetup info 
Name:              pvfoo
State:             ACTIVE
Tables present:    LIVE
Open count:        3
Event number:      0
Major, minor:      254, 1
Number of targets: 1

Name:              vgfoo-lvfoo
State:             ACTIVE
Tables present:    LIVE
Open count:        0
Event number:      0
Major, minor:      254, 3
Number of targets: 1
UUID: [snipped]

Name:              vgfoo-lvbar
State:             ACTIVE
Tables present:    LIVE
Open count:        1
Event number:      0
Major, minor:      254, 2
Number of targets: 1
UUID: [snipped]

> ii) use 'lsof' to find out who has opened the device.

# lsof /dev/mapper/vgfoo-lvfoo
# lsof /dev/mapper/vgfoo-lvbar
COMMAND     PID     USER   FD   TYPE DEVICE     SIZE    NODE NAME
[snipped many lines of output]

# lvchange -a n vgfoo/lvfoo
  LV vgfoo/lvfoo in use: not removing

Hmmmm.  Looks to me like it shouldn't be complaining.  I
don't know if this would affect anything at the lv layer,
but the only unusual thing here is that my pv happens to be
built on top of device mapper (dm-crypt).  Everything has
been working fine except for lv and vg deactivation.

mossmann

      reply	other threads:[~2004-03-10 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 18:58 [linux-lvm] lvm2 vgchange -a n problem Michael Ossmann
2004-03-08  4:36 ` Joe Thornber
2004-03-10 16:14   ` Michael Ossmann [this message]

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=20040309234328.GA6481@ossmann.com \
    --to=mike@ossmann.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 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.