On Thu, 2010-07-22 at 20:04 +0200, Volker Lendecke wrote: > On Thu, Jul 22, 2010 at 11:02:04AM -0700, Jeremy Allison wrote: > > On Thu, Jul 22, 2010 at 12:58:50PM -0400, Trond Myklebust wrote: > > > > > > That would make it impossible to export the filesystem with NFSv2 and > > > v3. They do rely on ctime checking for certain operations (e.g. deciding > > > when to invalidate access and acl caches). NFSv4 needs this too if the > > > filesystem has no dedicated change attribute. > > > > > > Still, I suppose the market for exporting the same filesystem with both > > > NFS and Samba is limited... > > > > Ask NetApp about that :-). They have built a rather large > > business on just that fact :-). > > Jeremy, how many hours have you spent getting "posix > locking" to the point where it is now? :-) > > Volker > > P.S: For those not aware, "posix locking = yes" is > cross-protocol byte range locking done by smbd to co-operate > with local processes and NFS. I said "limited", not "non-existent". The fact remains that most of us would be hard pressed to name an application that requires you to share the same dataset to both Windows/CIFS and posix NFS clients. Everything from ACL models through caseless vs case-aware filesystems and Windows vs posix locking semantics tends to discourage mixing the two environments. Trond -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
