Re: [Fwd: [Bug 136] New: FSID returned from statvfs always 0]

If this feature is to have any value, should not the fsid remain stable
as the disk gets moved around the machine?

To have _any_ value would be an overstatement.  Today's FSID (always zero)
has no value.  An FSID that works only in machines where the disks never
move would have more value than that.

But as long as we're talking about designs that solve the entire problem,
don't forget this aspect too:  A perfect FSID must be stable as the
filesystem is moved from one disk to another while the disks stay put.
And, more importantly, must change when you replace the contents of a disk
with a new or different filesystem.