Is this happening because the device number is assigned first to one value initially, and later to another value -- all during a single hierarchy traversal?
If so, I'll have to push this back into the kernel/file-system court.
I think we'll have to make the file system present a consistent device and inode number for any file it serves.
Hello,
Is this happening because the device number is assigned first to one value initially, and later to another value -- all during a single hierarchy traversal?
If so, I'll have to push this back into the kernel/file-system court.
I think we'll have to make the file system present a consistent device and inode number for any file it serves.