> Code branch - Ganesha 2.2.0-stable > > On windows 2008 R2 nfsv3 mount, when I try to save file it fails with > NLM_DENIED, On windows it show error "The process cannot access the file > because another process has locked a portion of the file". > while this message, I saw nlm4_Share --> state_nlm_share --> > state_share_check_conflict fails with error, "deny write denied by existing > access write" and returns 'conflict' > > I wonder should there be check for same owner in > state_share_check_conflict, If same owner is requesting write should it > result in conflict? > > There is no other process on windows machine, other than current open > notepad session for given file. > > Any one know reason/patch for this behavior.
Could you try again with 2.4 on FSAL_VFS? Unfortunately I don't have a Windows client to test, and Windows is the only NFS v3 client I know of that uses NLM_SHARE. I would love to understand it's usage pattern because the NLM spec is not clear on how NLM_SHARE should behave if the owner already has a share. There is no documentation of share upgrade/downgrade semantics. Thanks Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
