On 11/06/98 11:50:43 you wrote:
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....
As I pointed out before, simply mounting .snapshot as it's own filesystem on the client will resolve this problem.
Bruce
In article 199811643710641@ix.netcom.com, you write: |> On 11/06/98 11:50:43 you wrote: |> > 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.... |> |> As I pointed out before, simply mounting .snapshot as it's own filesystem |> on the client will resolve this problem.
No it won't.
The .snapshot will still be there and will still suffer this problem when someone uses it.
And it would leave me with another issue - how to setup automount maps to do the actual mounts in some consistent way.