<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NFS V4 locking in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/nfs-v4-locking/m-p/5384653#M53346</link>
    <description>&lt;P&gt;Yes the rpc.nfsd demons are still there under NFS Version 4 .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, I have tried V4 locking on a RHEL5 test server&lt;/P&gt;&lt;P&gt;and that all works as expected..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Someone related to me&amp;nbsp; on the Red Hat forums that&lt;/P&gt;&lt;P&gt;they had had to revert to NFS V3 under RHEL4.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;So I guess it is some sort of kernel issue, that&lt;/P&gt;&lt;P&gt;will,likely, never be resolved by now.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Nov 2011 12:36:04 GMT</pubDate>
    <dc:creator>David Nixon</dc:creator>
    <dc:date>2011-11-08T12:36:04Z</dc:date>
    <item>
      <title>NFS V4 locking</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nfs-v4-locking/m-p/5383325#M53340</link>
      <description>&lt;P&gt;&amp;nbsp; Have been testing some NFS version 4 exports from a RHEL 4.8 server&lt;/P&gt;&lt;P&gt;and its quckly become apparent that there are issues with locking.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Basically the fcntl(2) and lockf(2) system call interfaces don't work.&lt;/P&gt;&lt;P&gt;On an V4 mount these calls always fail with errno ENOLCK - no&lt;/P&gt;&lt;P&gt;locks available.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Contrary to what is stated by its man page, flock(2)&amp;nbsp; does work over&lt;/P&gt;&lt;P&gt;NFS V3&amp;nbsp; or V4, at least from version FC13 and Scientific Linux clients.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone shed any light on the basic issue?&amp;nbsp; I am wondering&lt;/P&gt;&lt;P&gt;if I need some Kernel update or other.. Currently running 2.6.18-164&lt;/P&gt;</description>
      <pubDate>Mon, 07 Nov 2011 11:59:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nfs-v4-locking/m-p/5383325#M53340</guid>
      <dc:creator>David Nixon</dc:creator>
      <dc:date>2011-11-07T11:59:11Z</dc:date>
    </item>
    <item>
      <title>Re: NFS V4 locking</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nfs-v4-locking/m-p/5384131#M53344</link>
      <description>&lt;P&gt;Do you have to have a demon running on the server like HP-UX?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Nov 2011 03:36:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nfs-v4-locking/m-p/5384131#M53344</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2011-11-08T03:36:15Z</dc:date>
    </item>
    <item>
      <title>Re: NFS V4 locking</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nfs-v4-locking/m-p/5384653#M53346</link>
      <description>&lt;P&gt;Yes the rpc.nfsd demons are still there under NFS Version 4 .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, I have tried V4 locking on a RHEL5 test server&lt;/P&gt;&lt;P&gt;and that all works as expected..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Someone related to me&amp;nbsp; on the Red Hat forums that&lt;/P&gt;&lt;P&gt;they had had to revert to NFS V3 under RHEL4.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;So I guess it is some sort of kernel issue, that&lt;/P&gt;&lt;P&gt;will,likely, never be resolved by now.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Nov 2011 12:36:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nfs-v4-locking/m-p/5384653#M53346</guid>
      <dc:creator>David Nixon</dc:creator>
      <dc:date>2011-11-08T12:36:04Z</dc:date>
    </item>
  </channel>
</rss>

