I think it would be nice to document in btrfs(5) the speciality that when having e.g.
…/subvol1/subvol2
and subvol1 is snapshotted, subvol2 remains in the created snapshot as empty but unusable directory, i.e. one cannot create files within it.
And perhaps also describe, that such – Andrei named them "orphan subvolume graft point" on the mailing list[0] – won't get send | received.
I could in principle provide a patch for that, but right now we don't have a section about snapshots or subvols, yet, so I wasn't really sure where you'd want to have such documentation.
If you can tell me how you'd like to have this, I could try to make a PR.
Hey.
I think it would be nice to document in
btrfs(5)the speciality that when having e.g.and
subvol1is snapshotted,subvol2remains in the created snapshot as empty but unusable directory, i.e. one cannot create files within it.And perhaps also describe, that such – Andrei named them "orphan subvolume graft point" on the mailing list[0] – won't get send | received.
I could in principle provide a patch for that, but right now we don't have a section about snapshots or subvols, yet, so I wasn't really sure where you'd want to have such documentation.
If you can tell me how you'd like to have this, I could try to make a PR.
Cheers, Chris.
[0] https://lore.kernel.org/linux-btrfs/ea6099a3cff73c20da032afaaeb446c0b12ec1da.camel@scientia.org/