I did, it was a case of going with a "known" set of bugs rather than a
potentially unknown set -- at this stage in our release cycle (just two
weeks off a long term supported release) we'd rather know the bugs ;-)
--
vol_id not run for entire-disk device breaks LVM across entire disk
https://bugs
Scott,
I saw in the 117-7 update you removed the partition condition from the
vol_id rule, I thought it was going to be changed to below.
ENV{DEVTYPE}=="partition", IMPORT{program}="vol_id --export $tempnode"
ENV{DEVTYPE}=="disk", ATTR{removable}=="0", IMPORT{program}="vol_id --export
$tempnode"
This bug was fixed in the package udev - 117-7
---
udev (117-7) hardy; urgency=low
* debian/patches/50-vol_id-on-entire-disk.patch:
- Run vol_id on the entire disk again. LP: #192794.
- The reason it was disabled upstream was to avoid the cases where
removable devices
Scott's udev upload approved for freeze exception.
--
vol_id not run for entire-disk device breaks LVM across entire disk
https://bugs.launchpad.net/bugs/192794
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Fri, 2008-04-11 at 09:23 +, Scott James Remnant wrote:
> Kay: you only get stale db entries and symlinks if the entire-disk
> changes? Does that happen often?
>
> Assumedly the db entries and symlinks get removed if the disk is
> removed?
Yes, every time you change the media, the "disk" c
Move back to udev, since that's where the bug is
** Changed in: udev (Ubuntu)
Status: Invalid => Confirmed
** Changed in: udev (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Scott James Remnant (keybuk)
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => Inv
Kay: you only get stale db entries and symlinks if the entire-disk
changes? Does that happen often?
Assumedly the db entries and symlinks get removed if the disk is
removed?
--
vol_id not run for entire-disk device breaks LVM across entire disk
https://bugs.launchpad.net/bugs/192794
You receive
On Fri, 2008-04-11 at 00:16 +, Brendan Dahl wrote:
> Another idea while the kernel change events are still being worked out; what
> about this line being added below the partition rule in
> 65-persistent-storage.rules:
> ENV{DEVTYPE}=="disk", ATTR{removable}=="0", IMPORT{program}="vol_id --e
On Thu, 2008-04-10 at 23:59 +, Scott James Remnant wrote:
> So what's the ENV check actually guarding against, if there are no
> events in the first place?
There are "add" events at creation/hotplug/coldplug time, which would
result in stale db entries/symlinks which would never be updated aga
scott, I don't yet fully understand the data/links/db thing, but the
result I've been able to see;
with that rule I suggested allowing disk types to export vol_id, every
time you insert a thumb drive whether or not lvm type, when you remove
the drive sdX is removed, however when you reinsert/inser
So what's the ENV check actually guarding against, if there are no
events in the first place?
--
vol_id not run for entire-disk device breaks LVM across entire disk
https://bugs.launchpad.net/bugs/192794
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
11 matches
Mail list logo
