News for hackers. Stuff that matters.

A comment on The Btrfs inode-number epic (part 1: the problem). Parent comment

Re:The Btrfs inode-number epic (part 1: the problem) by magicalhippo on Tuesday August 24, 2021 @03:43PM (#28293910)
I'm no expert so maybe I'm missing something.

To me it seems that ZFS snapshots represents a similar challenge[1] given that the snapshots can be accessed through the .zfs directory, and that ZFS also plays tricks[2] with the inodes.

[1]: https://docs.oracle.com/cd/E19253-01/819-5461/gbiqe/index.ht...

[2]: http://mikeboers.com/blog/2019/02/21/zfs-inode-generations

[ Parent | on HN ]
Re:The Btrfs inode-number epic (part 1: the problem) by rincebrain on Tuesday August 24, 2021 @04:30PM (#28294582)
They're always explicit mounts on ZFS. (Even the .zfs directory triggers mounting on access of things under snapshot/.)
[ Parent | on HN ]
Re:The Btrfs inode-number epic (part 1: the problem) by AndrewDavis on Tuesday August 24, 2021 @08:58PM (#28296914)
As a tangent, what's interesting is whether `mount` shows the mountpoint.

If you cd into a snapshot on FreeBSD it does not get listed in calls to `mount` but does on ZoL.

edit: i have not tested this since FreeBSD rebased on ZoL

[ Parent | on HN ]