From: Peter Rajnoha <prajnoha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] dev node change
Date: Wed, 11 Dec 2013 09:46:27 +0100 [thread overview]
Message-ID: <52A82663.1070605@redhat.com> (raw)
In-Reply-To: <CAFrGbuWboS=2RoheSc7w0zLTnhvOQwq7N8UTfOe8TruLOFWecg@mail.gmail.com>
On 12/10/2013 03:33 PM, Alessandro MACUZ wrote:
> 2013/12/10 Peter Rajnoha <prajnoha@redhat.com <mailto:prajnoha@redhat.com>>
>
> On 12/09/2013 04:13 PM, Umar Draz wrote:
> > Hi All
> >
> > I have a SCSI share which i am using linux initiator on my
> ubuntu. Its
> > available for me in /dev/sdb
> >
> > No I have created lvm group using the /dev/sdb. Today I just logut and
> > login my scsi share but this time ubutnu gave me this as /dev/sdc
> > instead of /dev/sdb.
> >
> > due to this my lvm group is stuck, and its giving me the error
> >
> > Input/output error
> >
> > on pvdisplay or vgdisplay,
> >
> > Any body help me how I can reslove this issue.?
> >
>
> You should always deactivate your LVM volumes before
> disconnecting the underlying iSCSI volumes and then when
> you reconnect the iSCSI back, activate the LVM volumes
> (or if autoactivation is used - meaning use_lvmetad=1
> is set in lvm.conf, this activation happens automatically).
>
> Alternatively, you can call vgchange --refresh when the
> iSCSI is connected back.
>
>
>
> Couldn't be used the identification of PV by UUID here? It should be
> better imo.
>
Well, this is about dm tables that represent the logical volumes
(you can check dmsetup table output). The PV UUID doesn't play a role
at this level - the PV UUID is just LVM abstraction that is using
device-mapper kernel capabilities.
And if the iSCSI is disconnected while there's anything on top of it
(in this case the LV), the major:minor pair (as well as the kernel name)
is reserved until all the stack above it is freed.
Then when the iSCSI is connected back (while the old major:minor is
still held by old mapping), kernel has no other choice just to assign
new major:minor pair. Therefore we need a refresh (or deactivation/activation)
which will generate a new mapping with the new major:minor pair of the
underlying PV (the iSCSI volume).
--
Peter
next prev parent reply other threads:[~2013-12-11 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 15:13 [linux-lvm] dev node change Umar Draz
2013-12-10 14:19 ` Peter Rajnoha
2013-12-10 14:33 ` Alessandro MACUZ
2013-12-11 8:46 ` Peter Rajnoha [this message]
2013-12-11 9:23 ` Umar Draz
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=52A82663.1070605@redhat.com \
--to=prajnoha@redhat.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.