I also see this race condition happen often when I open up and
manipulate nested LVM devices.
For example, an LV is partitioned and one of the partitions inside is a
PV. A kpartx -a is run to activate the partitions, vgimportclone is run
to rename the VG inside that nested PV, and as
Has this ever truly been resolved? I believe I am seeing this same bug
with 14.04 and failing to resolve it even with the workarounds listed
here. After unstack I'm left with a logical volume which I cannot delete
or deactivate.
--
You received this bug notification because you are a member of
** Tags added: quantal raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
Title:
udev rules make it impossible to deactivate lvm volume group with
vgchange -an
To manage notifications
This also stops vgimportclone (which I used to import LVM VGs from
virtual machines) from working correctly, eg:
# lvcreate -n testsnap -L 10G --snapshot vmdata/sirius-test-nz-db
Logical volume testsnap created
# kpartx -va /dev/mapper/vmdata-testsnap
add map vmdata-testsnap1 (252:238): 0
It looks that Precise is affected also in combination with the LVM
resource agent from the pacemaker cluster manager (package: resource-
agents): In a simple test setup (LVM on top of an DRBD device) I was not
able to reliable migrate the volume group from one node to the other
until I disabled
Interesting. Precise - Quantal saw a very big lvm2 update. There were
changes done to udev handling and maybe some of it needs to be reverted.
It's interesting that dmsetup remove works, and maybe lvchange should
act more like dmsetup does.
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned)
Hi,
thank you Pavel, the tip with dmsetup remove works fine (using
/dev/mapper/vg_.).
Nasty bug though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
Title:
udev rules make it
Same problem here. Another workaround is to use 'sudo dmsetup remove /dev/dm-X'
instead of 'sudo lvchange -a n vg/lv'.
As @Dr_Jekyll has stated Ubuntu 12.04 is not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Thanks Martin, that works for me as well. Still, a real fix would be great.
Have a good week,
Christoph
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
Title:
udev rules make it
Hi,
it's been a month now, can we do anything to promote this bug? Even if it
won't be fixed in 12.10, can we somehow make sure it receives some attention
for 13.04?
Thanks,
Christoph
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
I would also like to get if fixed soon.
Nevertheless I found at least a workaround which works for my systems.
The workaround is as follows.
sudo umount /mnt # asume the drive in question is mounted under /mnt
sudo service udev stop
sudo lvchange -a n LV-name
sudo cryptsetup luksClose
Tagging with regression-release because this works in 12.04. Thanks to
@Dr_Jekyll for testing!
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
Title:
udev
Hello,
quick follow-up: I confirmed that Ubuntu 12.04 does work as expected, it is
possible to make a logical volume unavailable with lvchange -an LV. I tested
this with the same LV as from 12.10.
Thanks,
Chris
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
Title:
udev
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: udev (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
Title:
udev
Hello everyone,
i made the same observations, on 12.10 Server. If there's anything i can do to
test or debug this, I'd love to.
Thanks,
Chris
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
Title:
udev rules make it impossible to deactivate lvm volume group
17 matches
Mail list logo
