vol_id: detects crypto_LUKS instead of ext3 UUID
Bug #93921 reported by
jens_acamedia
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
e2fsprogs (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
udev (Ubuntu) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
Binary package hint: e2fsprogs
on my updated feisty i do
root@bigboy:~# vol_id -u /dev/hda2
18942279-
root@bigboy:~# findfs UUID=18942279-
findfs: Unable to resolve 'UUID=18942279-
root@bigboy:~#
this seems strange to me. could this be connected with the reason why i cannot see hda2 as mounted when i do "mount" or "df"
i know hda2 is mounted since its my root fs and it is referenced by UUID in fstab. this is confusig me but perhaps im missing something...
Changed in e2fsprogs: | |
status: | Confirmed → Invalid |
Changed in udev: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in udev: | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
very much the same on my machine.
"ls -l ... " gives correct output but findfs and df have a problem