Bug 130224 - volume uuids (as displayed with lshal) are not unique
Summary: volume uuids (as displayed with lshal) are not unique
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Danny Kukawka
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-24 07:15 UTC by Ulrich Windl
Modified: 2005-10-24 09:51 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2005-10-24 07:15:33 UTC 
Release notes suggest to mount removable devices async by using the volume.uuid
and lshal. However the uuids aren't unique. Specifically some volumes have an
empty volume.uuid:
> lshal |grep volume.uuid
lshal version 0.5.4
  volume.uuid = ''  (string)
  volume.uuid = ''  (string)
  volume.uuid = '3f832370-4f7c-4a1a-bc2b-d9162dce0a14'  (string)
  volume.uuid = ''  (string)
Comment 1 Danny Al-Gaaf 2005-10-24 09:51:45 UTC 
This happens because the device has no volume uuid (see: http://cvs.freedesktop.org/*checkout*/hal/hal/doc/spec/hal-spec.html for volume.uuid).