On Fri, Jul 30, 2021 at 02:23:44PM +0800, Qu Wenruo wrote: > OK, forgot it's an opt-in feature, then it's less an impact. > > But it can still sometimes be problematic. > > E.g. if the user want to put some git code into one subvolume, while > export another subvolume through NFS. > > Then the user has to opt-in, affecting the git subvolume to lose the > ability to determine subvolume boundary, right? Totally naive question: is it be possible to treat different subvolumes differently, and give the user some choice at subvolume creation time how this new boundary should behave? It seems like there are some conflicting priorities that can only be resolved by someone who knows the intended use case. --b.
