Messages in this thread |  | | Subject | Re: [PATCH 02/18] xstat: Add a pair of system calls to make extended file stats available [ver #6] | | From | Trond Myklebust <> | | Date | Sat, 31 Jul 2010 15:03:52 -0400 |
| |
On Sat, 2010-07-31 at 12:41 -0600, Andreas Dilger wrote: > On 2010-07-30, at 12:11, Trond Myklebust wrote: > > Your Mac has a perfectly functional CIFS client, as do your Linux boxes. > > They both interoperate just fine with Samba, and would presumably > > continue to do so if someone were to decide to reuse the ctime field on > > your Samba box as storage for a create time. > > CIFS doesn't support symlinks (they just appear as the referenced file), so I've had applications that scan the filesystem recurse indefinitely due to symlinked directories on a CIFS share appearing as hard-linked directories on the client. This doesn't happen when the filesystem is accessed via NFS.
Sigh... So please explain how it would be useful to export that particular filesystem through _both_ CIFS and NFS?
My point was that in most circumstances you want to export either through CIFS or through NFS, but very rarely both.
I also made the point that converting ctime into a creation time would break NFS, but it would be a limited breakage, mainly affecting the client's ability to detect ACL changes, and possibly causing the inode to get temporarily updated with stale attribute information on occasion due to out-of-order RPC replies.
Trond
|  |