Hi James, I'm targeting this fix for build snv_124. It's strange that this issue hasn't been reported before, because our NFS4 server has always (mis)behaved this way since NFS4 first arrived in the first S10 release. Each year we attend Connectathon and do interop testing with Linux NFS implementors (and we haven't heard of this before), so it makes me wonder if a recent Linux NFS client change might be exposing our misbehavior.
Jeff On Aug 24, 2009, at 8:49 PM, James Lever wrote: > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6854659 > > Just wondering if anybody knows what's happening with this bug? > It's the only thing keeping us from moving to NFSv4 (which I > desperately need to do to avoid hundreds of lines dozens of servers / > etc/fstab that are quite unmaintainable) > > We're badly affected by this bug due to the way that subversion > creates its lock files by using O_EXCL to create .svn/lock and then > populating .svn/entries with the mtime value which makes doing any > checkouts on an NFSv4 mounted filesystem (from linux) a no-go. > > cheers, > James > _______________________________________________ > nfs-discuss mailing list > nfs-discuss at opensolaris.org
