[Box Backup] inode, fsid, and OS dependencies

[Joe Krahn]

If Win32 uses a VolumeSerialNumber, shouldn't we do the same in 
BSD/Linux? Actually, I've been thinking it would be good to use more 
than one identifier and complain if they don't all match:

1) Mount point: Windows also has a Mountpoint entry.
2) Volume label: I think all OSes/filesystems have this.
3) Serial number or GUID/UUID: Available in most cases.

Number 3 is the most reliable identifier, but may not always be 
possible. This may be a bit 'overkill', but it's quick.

Also, not just in Windows, has anyone worked with Logical volumes 
spanning more than one drive? Are there any cases where you get status 
info about the physical disk instead of the virtual/logical disk?

Joe

Nick Knight wrote:
> Exactly - it uses the volume id for Bens mount point
> 
> -----Original Message-----
> From: boxbackup-admin@fluffy.co.uk [mailto:boxbackup-admin@fluffy.co.uk]
> On Behalf Of Joe Krahn
> Sent: 21 December 2004 05:28
> To: boxbackup@fluffy.co.uk
> Subject: Re: [Box Backup] inode, fsid, and OS dependencies
> 
> Nick Knight wrote:
> 
>>The file index is obtained by calling GetFileInformationByHandle and
>>combining the low and high part of the serial number.
>>
>>For the Win32 version I have implemented the stat functions which
>>populate the inode fields.
>>
> 
> OK... I didn't see that function; It's like an extended version of 
> GetFileAttributes. I see it also has dwVolumeSerialNumber. Is that used 
> to verify unique filesystems? I think it would be good for all boxbackup
> 
>   platforms to include some sort of disk/filesystem ID or label to 
> verify that the right filesystem is there.
> 
> Joe Krahn
> 
> _______________________________________________
> boxbackup mailing list
> boxbackup@fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup
> 
> 
> _______________________________________________
> boxbackup mailing list
> boxbackup@fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup