Hugh McIntyre wrote: > But this raises the point that if these special reparse symlinks were > implemented such that the reparsing also happened when the filesystem is > mounted locally via mount_zfs or mount_lofs, not just remotely over CIFS > or NFSv4, then most of the issues would go away. > > In other words if open(), stat(), nftw(), and similar system calls > locally on the server hosting the files (including LOFS) access the > linked-to file, most code will think the link is OK. Since in this > case, "find -L" should point to the target of the reparse point (which > hopefully exists).
The project team is pretty interested in semantics seen by NFS and CIFS clients, not local semantics, so we're not terribly excited to do work to make local access act like that; I get the motivations, but it's a whole lot of work. There are also difficulties. We know we will want to set up a reparse point that projects the same namespace for both NFS and CIFS, and it isn't obvious what client code we would bridge into locally. We would also like to be able to back up reparse points, so local processes need to access them without interpretation. Rob T
