In article 364225F4.47D356C@dnrc.bell-labs.com, you write: |> |> Wouldn't this be solved if ~snapshot appeared as a shortcut in CIFS, and |> as a symbolic link in NFS?
A symbolic link to what? Something that exists, so the "problem" is still there.
Mind you, I'm not exactly sure what the problem is, as the .snapshot directory only *has* to appear at mountpoints (see below) and that is the default (I think - this is for NFS). Is the problem that you have separate mountpoints for individual users HOME directories?
It would be even better if you could get rid of the one at the mountpoint as well, thne find would never have a problem (but you could still get to .snapshot by name - it becomes and entry you get if you ask for it, but not an entry when you read the directoiry contents). However, when I did turn them off (long time ago) I found that df at the NetApp console would no longer give me any snapshot info. Anyone know whether that bug/feature has been fixed (it was reported...)?
Also, one thing that I would like to see changed (if it makes sense) is for the NetApp servers to return different inodes for snapshot entries (OR in teh snapshot number at the top-end?). The reason for this is that some versions (egL GNU) of diff seem to check fs/inode info, and if they find they are the same they don't bother to do any diff'ing....