From: Peter Rajnoha <prajnoha@redhat.com>
To: lvm-devel@redhat.com
Subject: vgrename omit renaming hidden volumes if vg is inactive -> thinpools will be inconsistent
Date: Fri, 08 Aug 2014 08:26:07 +0200 [thread overview]
Message-ID: <53E46D7F.10203@redhat.com> (raw)
In-Reply-To: <53E3D623.7040606@mglug.de>
On 08/07/2014 09:40 PM, Oliver Rath wrote:
> Hi list,
>
> ive probably found a bug in lvm2 (testet on commit hash
> 6320c3b9052004397faf1687198756ac7914fecc):
>
> if i rename an inactive vg (vgchange -an vg), then the hidden volumes
> like /dev/mapper/vg-mypool_tdata ..tmeta ..tpool arent renamed in
> /dev/mapper/..
>
Inactive VG should not have any /dev/ content. If it remained after
deactivation, it seems to be a bug in node/symlink handling under /dev.
A few questions then:
- what distro is this?
- are you using udev rules from lvm2 git repo too?
- what are the lvm.conf values for these settings:
- activation/udev_sync
- activation/udev_rules
- activation/verify_udev_operations
- what udev (or systemd+udev) version is being used
- are all the items found in /dev/mapper symlinks (not direct block dev nodes)?
- are there dangling symlinks found in /dev/mapper for the LVs from deactivated VG?
--
Peter
next prev parent reply other threads:[~2014-08-08 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 19:40 vgrename omit renaming hidden volumes if vg is inactive -> thinpools will be inconsistent Oliver Rath
2014-08-08 6:26 ` Peter Rajnoha [this message]
2014-08-08 8:51 ` Oliver Rath
2014-08-08 14:30 ` configuration details [was Re: vgrename omit renaming hidden volumes if vg is inactive -> thinpools will be inconsistent] Oliver Rath
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=53E46D7F.10203@redhat.com \
--to=prajnoha@redhat.com \
--cc=lvm-devel@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.