Hi Jeff, Thanks much for your inputs. I have tried to get some info from samba list but no luck. My proposed system is a fileserver which is supposed to be share point for both windows and Linux ( CIFS and NFS). So I can't point one particular application. Basically I want to rule out file corruption while sharing single file across multiple protocols. Thanks Anoop > -----Original Message----- > From: Jeff Layton [mailto:jlayton@xxxxxxxxxx] > Sent: Wednesday, May 20, 2009 9:54 PM > To: Anoop P.A. > Cc: linux-nfs@xxxxxxxxxxxxxxx > Subject: Re: NFS-CIFS locking > > On Wed, 20 May 2009 09:12:24 -0700 > "Anoop P.A." <Anoop_P.A@xxxxxxxxxxxxxx> wrote: > > > Hi Jeff, > > > > Thanks for your reply. Basically what I want is "the file which is used > under CIFS share should not get overwritten from a nfs share and vice > versa." . I might be looking for mandatory file locking in nfs share. > > > > That may be tricky. > > Mandatory locking under unix is rather rare. Most unix apps use > advisory locking. Windows however uses mandatory locking pretty much > exclusively. The semantics of windows locks are quite different -- they > don't necessarily map 1:1, particularly when you get into how > overlapping byte ranges are handled and such. > > The best advice I can offer is to understand how your apps use locking > and to do some testing to simulate those use cases. That should help > outline where the differences are. > > Again, the samba lists are probably a better forum for this discussion. > The developers that lurk on those lists generally have a good > understanding of the subtleties involved in mapping file locks between > the two platforms. > > With more specific questions you may be able to get more helpful > answers as well. > > -- > Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
