Identifying disks, drives and network mounts

[John Van Ostrand]

On Wed, 2006-09-06 at 12:49 -0400, Madison Kelly wrote:

> Hi all,
> 
>    I have been struggling with this problem for a couple of years now 
> (yes, really!) and have tried a couple different solutions that were 
> never as robust as I would like. So I am hoping some brainiac here might 
> have an idea! :)

...

>    Any ideas (or corrections to my assumptions) would be greatly 
> appreciated! I realize I may need to settle on a combination of 
> solutions, but I'd like to keep that to a minimum, too.


This is a problem that has really only surfaced relatively recently
(last 10 years). Most new file systems and volume managers should
support some form of unique ID.

I think you are not going to find a single solution. You've already
identified the ext2/3 UUID from blkid.

If you are dealing with LVM volumes you could use the UUIDs there.
(vgdisplay or lvdisplay.)

You may just have to find UUIDs in other file systems. Failing that the
hidden file is a good idea, although like you said, not reliable.
Finally you could use fs data like file system type, sizes, creation
date, etc to come up with a pseudo unique ID.

-- 
John Van Ostrand
         Net Direct Inc.
 
Chief Technology Officer
564 Weber St. N. Unit 12
   Waterloo, ON N2L 5C6 
 map 
john-Da48MpWaEp0CzWx7n4ubxQ at public.gmane.org
        Ph: 519-883-1172
 ext.5102
Linux Solutions / IBM
Hardware
        Fx: 519-883-8533
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20060906/02c25f93/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://gtalug.org/pipermail/legacy/attachments/20060906/02c25f93/attachment.sig>