[dm-devel] Question about dmevents

[Wood, Brian J]

>-----Original Message-----
>From: dm-devel-bounces at redhat.com [mailto:dm-devel-bounces at redhat.com]
On
>Behalf Of Alasdair G Kergon
>Sent: Sunday, July 22, 2007 4:16 AM
>To: device-mapper development
>Subject: Re: [dm-devel] Question about dmevents
>
>On Sun, Jul 22, 2007 at 10:43:17AM +0200, Peter Rockai wrote:
>> In fact, when using theh libdevmapper-event library, the client-side
>> code should already fail, if a device has no uuid. In practice, this
>> means that uuid-less devices cannot be monitored, but that is
probably
>> a case that is not really important (or is it?).
>> I would probably prefer to just document this as requirement and keep
>> things as they are. Comments?
>
>That all makes sense to me.

Agreed :)


>
>  name = user-friendly reference; can be changed at will
>  uuid = software-friendly reference, a constant for the life of the
device
>
>If we have existing software not setting up uuids then those programs
need
>investigating.
>

I have a question though, not being too familiar with the device-mapper
core code. When I load a fresh system using FC7 on a raid1 volume (for
example) I never see a prompt during the installation asking if I would
like to have a UUID assigned. After the install I check and there isn't
one assigned by default. If I then add some disks to the system and
decide to install an LVM2 mirror I do this using the command line and
there is a UUID assigned by default. Is this also a bug in the
installer? Or is there a way I can assign a UUID to an already existing
system? In the documentation it says I would have to delete my volume
group and rebuild it to assign a UUID is this correct? If so how can a
fresh system get a UUID?

Thank you for all the help :) 

Brian Wood
Intel Corporation 
Digital Enterprise Group
Manageability & Platform Software Division
brian.j.wood at intel.com

>Alasdair
>--
>agk at redhat.com
>
>--
>dm-devel mailing list
>dm-devel at redhat.com
>https://www.redhat.com/mailman/listinfo/dm-devel