Re: A Third perspective on BTRFS nfsd subvol dev/inode number issues.
From: J. Bruce Fields <hidden>
Date: 2021-08-02 20:41:27
Also in:
linux-btrfs, linux-fsdevel
From: J. Bruce Fields <hidden>
Date: 2021-08-02 20:41:27
Also in:
linux-btrfs, linux-fsdevel
On Mon, Aug 02, 2021 at 03:32:45PM -0500, Patrick Goetz wrote:
On 8/2/21 7:39 AM, J. Bruce Fields wrote:quoted
On Mon, Aug 02, 2021 at 02:18:29PM +1000, NeilBrown wrote:quoted
For btrfs, the "location" is root.objectid ++ file.objectid. I think the inode should become (file.objectid ^ swab64(root.objectid)). This will provide numbers that are unique until you get very large subvols, and very many subvols.If you snapshot a filesystem, I'd expect, at least by default, that inodes in the snapshot to stay the same as in the snapshotted filesystem.For copy on right systems like ZFS, how could it be otherwise?
I'm reacting to Neil's suggesting above, which (as I understand it) would result in different inode numbers. --b.