Ubuntu
lvm2 package

udev rules should not automatically active logical volumes

Bug #133905 reported by Jerome Haltom
4
Affects Status Importance Assigned to Milestone
lvm2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: lvm2

Currently lvm2 installs a udev rules fine which runs vgchange -a y on any detected block devices. This isn't exactly desired. Activing the volumn groups automatically is not always waht the user expects to happen when hot plugging a SATA drive, for instance. The volume group should be created, but not activated. vgscan accomplishes this.

The one exception to this rule is from the initramfs when trying to locate root. I think it would be safe to have the initramfs auto activate volumes, but not the main system. This means the rules between the two might not be the same.

Revision history for this message
Bart Verwilst (verwilst) wrote :

lvm2 should automatically execute vgchange -a y IMO. My xen hosts all have a lv as root, and now /etc/xen/auto/* hosts aren't started anymore since /dev/<myvg> isn't active when booting..

Revision history for this message
Michael Brunton-Spall (bruntonspall) wrote :

As indicated in bug #139337 turning off this feature breaks your system if critical partitions such as /home or /usr are LVM

Revision history for this message
Jerome Haltom (wasabi) wrote :

Okay, I'd like to add additional information then. If you activate a VG with the same name as an existing VG, as far as I can tell, none of the user space tools can differentiate between the two. Since people tend to name VGs the same between systems (vg0, VolGroup0), simply removing a drive from one LVM system and putting it into another is enough to get you into this situation.

I would agree to close this bug if conflictingly named VGs were not activated by default. Or at all, until somebody changes the name.

Revision history for this message
xteejx (xteejx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in lvm2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Evan Broder (broder) wrote :

The LVM udev rules still call vgchange -a y, so the scenario described in the bug report definitely still exists.

Changed in lvm2 (Ubuntu):
status: Incomplete → New
Revision history for this message
xteejx (xteejx) wrote :

Thank you. Can you just confirm which version of Ubuntu you are using please?

Changed in lvm2 (Ubuntu):
status: New → Incomplete
Revision history for this message
xteejx (xteejx) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in lvm2 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.