<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:39:13 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-4050] NFS reexport issue</title>
                <link>https://jira.whamcloud.com/browse/LU-4050</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Reexport works but in kernel messages logged the following:&lt;br/&gt;
Lustre: ctl-lustre-MDT0000: super-sequence allocation rc = 0 [0x0000000200000400-0x0000000240000400):0:mdt&lt;br/&gt;
LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can&apos;t get object attrs, fid &lt;span class=&quot;error&quot;&gt;&amp;#91;0x200000400:0x1:0x0&amp;#93;&lt;/span&gt;, rc -2&lt;br/&gt;
LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can&apos;t get object attrs, fid &lt;span class=&quot;error&quot;&gt;&amp;#91;0x200000400:0x1:0x0&amp;#93;&lt;/span&gt;, rc -2&lt;br/&gt;
LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can&apos;t get object attrs, fid &lt;span class=&quot;error&quot;&gt;&amp;#91;0x200000400:0x1:0x0&amp;#93;&lt;/span&gt;, rc -2&lt;br/&gt;
LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can&apos;t get object attrs, fid &lt;span class=&quot;error&quot;&gt;&amp;#91;0x200000400:0x1:0x0&amp;#93;&lt;/span&gt;, rc -2&lt;br/&gt;
LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can&apos;t get object attrs, fid &lt;span class=&quot;error&quot;&gt;&amp;#91;0x200000400:0x1:0x0&amp;#93;&lt;/span&gt;, rc -2&lt;br/&gt;
LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can&apos;t get object attrs, fid &lt;span class=&quot;error&quot;&gt;&amp;#91;0x200000400:0x1:0x0&amp;#93;&lt;/span&gt;, rc -2&lt;br/&gt;
LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) Skipped 1 previous similar message&lt;br/&gt;
LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) can&apos;t get object attrs, fid &lt;span class=&quot;error&quot;&gt;&amp;#91;0x200000400:0x1:0x0&amp;#93;&lt;/span&gt;, rc -2&lt;br/&gt;
LustreError: 3819:0:(llite_nfs.c:105:search_inode_for_lustre()) Skipped 2 previous similar messages&lt;/p&gt;</description>
                <environment>RHEL 6.4, Lustre from master at 02a976b &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3974&quot; title=&quot;Support for linux 3.11 kernel&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3974&quot;&gt;&lt;strike&gt;LU-3974&lt;/strike&gt;&lt;/a&gt; libcfs: replace num_physpages with totalram_pages&lt;br/&gt;
</environment>
        <key id="21237">LU-4050</key>
            <summary>NFS reexport issue</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="dmiter">Dmitry Eremin</assignee>
                                    <reporter username="dmiter">Dmitry Eremin</reporter>
                        <labels>
                    </labels>
                <created>Wed, 2 Oct 2013 15:40:26 +0000</created>
                <updated>Tue, 3 Jun 2014 12:45:39 +0000</updated>
                            <resolved>Wed, 23 Oct 2013 08:37:19 +0000</resolved>
                                    <version>Lustre 2.5.0</version>
                                    <fixVersion>Lustre 2.5.0</fixVersion>
                    <fixVersion>Lustre 2.6.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>11</watches>
                                                                            <comments>
                            <comment id="68156" author="dmiter" created="Wed, 2 Oct 2013 15:45:07 +0000"  >&lt;p&gt;Also listing of files is not refreshed until something changed on NFS share side. You can create a lot of files on Lustre but those files will be not visible until create something on NFS.&lt;/p&gt;</comment>
                            <comment id="68171" author="adilger" created="Wed, 2 Oct 2013 17:32:11 +0000"  >&lt;p&gt;It is worthwhile to check if fid &lt;span class=&quot;error&quot;&gt;&amp;#91;0x200000400:0x1:0x0&amp;#93;&lt;/span&gt; actually exists or not.  If this is a deleted file and NFS is just requesting attributes for a stale file handle then we should probably just turn this console error message off.&lt;/p&gt;</comment>
                            <comment id="68183" author="dmiter" created="Wed, 2 Oct 2013 18:35:50 +0000"  >&lt;p&gt;It looks just requesting attributes for a removed file.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;# mkdir /mnt/lustre/2
# lfs path2fid /mnt/lustre/2
[0x200000400:0x9b9:0x0]
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;[ Make file or dir on NFS share to sync ]&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;# dmesg -c
# rm -rf /mnt/lustre/2
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;Re-read from NFS share (just ls)&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;# dmesg -c
LustreError: 3815:0:(llite_nfs.c:105:search_inode_for_lustre()) can&apos;t get object attrs, fid [0x200000400:0x9b9:0x0], rc -2
LustreError: 3815:0:(llite_nfs.c:105:search_inode_for_lustre()) Skipped 4 previous similar messages
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The error message will appear until make file or dir on NFS share to sync.&lt;/p&gt;</comment>
                            <comment id="68217" author="adilger" created="Thu, 3 Oct 2013 07:01:06 +0000"  >&lt;p&gt;I think in this case that the console message should just be D_INFO for -ENOENT, or maybe always?&lt;/p&gt;

&lt;p&gt;As for the NFS refresh problem, I think that is a bug?  Shouldn&apos;t NFS revalidate the directory after a few seconds?&lt;/p&gt;</comment>
                            <comment id="68238" author="dmiter" created="Thu, 3 Oct 2013 14:51:31 +0000"  >&lt;p&gt;It&apos;s synced by timeout after about 1,5 min. It&apos;s not convenient for user I think. I measure the time when NFS observe that something changed in directory.&lt;/p&gt;

&lt;p&gt;changed time: 18:40:53.694375047&lt;br/&gt;
observe time: 18:41:23.707787906&lt;/p&gt;

&lt;p&gt;Is this bug?&lt;/p&gt;</comment>
                            <comment id="68246" author="dmiter" created="Thu, 3 Oct 2013 15:49:47 +0000"  >&lt;p&gt;Time of modification is not changed after directory creation.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;  File: `/mnt/lustre/export&apos;
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 2c54f966h/743766374d    Inode: 144115205255727587  Links: 4
Access: (0777/drwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-03 19:38:54.000000000 +0400
Modify: 2013-10-03 19:41:10.000000000 +0400
Change: 2013-10-03 19:41:10.000000000 +0400

mkdir /mnt/lustre/export/ack

  File: `/mnt/lustre/export&apos;
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 2c54f966h/743766374d    Inode: 144115205255727587  Links: 5
Access: (0777/drwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-03 19:38:54.000000000 +0400
Modify: 2013-10-03 19:41:10.000000000 +0400
Change: 2013-10-03 19:41:10.000000000 +0400
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="68387" author="pjones" created="Fri, 4 Oct 2013 17:07:09 +0000"  >&lt;p&gt;Fixing message patch &lt;a href=&quot;http://review.whamcloud.com/#/c/7850/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/7850/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="68388" author="adilger" created="Fri, 4 Oct 2013 17:16:40 +0000"  >&lt;p&gt;I suspect that the UPDATE IBITS lock is not being revoked or similar, so the Lustre client is incorrectly caching the timestamps.&lt;/p&gt;</comment>
                            <comment id="68420" author="jhammond" created="Fri, 4 Oct 2013 21:51:54 +0000"  >&lt;p&gt;If the UPDATE lock is not being revoked then why does the link count reported by stat change?&lt;/p&gt;</comment>
                            <comment id="68422" author="jhammond" created="Fri, 4 Oct 2013 22:46:53 +0000"  >&lt;p&gt;Dmitry, could you clarify your reproducer? Could you also post your /etc/exports and the output of mount on all relevant nodes?&lt;/p&gt;</comment>
                            <comment id="68434" author="adilger" created="Sat, 5 Oct 2013 05:05:29 +0000"  >&lt;p&gt;Could this be related to &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3240&quot; title=&quot;The link count is not updated after the mkdir&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3240&quot;&gt;&lt;del&gt;LU-3240&lt;/del&gt;&lt;/a&gt; (patch &lt;a href=&quot;http://review.whamcloud.com/6460)?&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/6460)?&lt;/a&gt;  I thought that patch was landed, but it is not.&lt;/p&gt;</comment>
                            <comment id="68439" author="dmiter" created="Sat, 5 Oct 2013 10:54:23 +0000"  >&lt;p&gt;I have checked with patch &lt;a href=&quot;http://review.whamcloud.com/6460&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/6460&lt;/a&gt;. It not fix the issue.&lt;/p&gt;

&lt;p&gt;The reproducer is following:&lt;/p&gt;

&lt;p&gt;On Lustre node I launch llmount.sh and then service nfs start.&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;# mount
l201u2@tcp:/lustre on /mnt/lustre type lustre (rw,user_xattr,flock)
# cat /etc/exports
/mnt/lustre 192.168.1.0/24(rw,no_root_squash,no_all_squash)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;On NFS node I mount NFS share:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;# mount
l201u2:/mnt/lustre on /net/l201u2/mnt/lustre type nfs (rw,nosuid,nodev,intr,sloppy,vers=4,addr=192.168.1.2,clientaddr=192.168.1.1)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Then launch test script on Lustre node:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;#!/bin/sh

D=/mnt/lustre/nfs

S=$(date +%T.%N)
&lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; [ ! -d $D/ask ]; &lt;span class=&quot;code-keyword&quot;&gt;do&lt;/span&gt;
    echo -n .
done
echo
stat $D
mkdir $D/ack &amp;amp;&amp;amp; echo mkdir $D/ack
stat $D
F=$(date +%T.%N)
echo Start: $S mkdir: $F
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The output is following:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;.............................................................
  File: `/mnt/lustre/nfs&apos;
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 2c54f966h/743766374d    Inode: 144115205255725057  Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 14:20:13.000000000 +0400
Modify: 2013-10-05 14:31:24.000000000 +0400
Change: 2013-10-05 14:31:24.000000000 +0400
mkdir /mnt/lustre/nfs/ack
  File: `/mnt/lustre/nfs&apos;
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 2c54f966h/743766374d    Inode: 144115205255725057  Links: 4
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 14:20:13.000000000 +0400
Modify: 2013-10-05 14:31:24.000000000 +0400
Change: 2013-10-05 14:31:24.000000000 +0400
Start: 14:31:21.749700343 mkdir: 14:31:24.247125347
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Then launch test script on NFS node:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;#!/bin/sh

D=/net/l201u2/mnt/lustre/nfs

S=$(date +%T.%N)
echo Start: $S
mkdir $D/ask
stat $D
&lt;span class=&quot;code-keyword&quot;&gt;while&lt;/span&gt; [ -d $D/ask ]; &lt;span class=&quot;code-keyword&quot;&gt;do&lt;/span&gt;
    &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; [ -d $D/ack ]; then
        stat $D
        F=$(date +%T.%N)
        echo mkdir: $F
        rm -rf $D/ask $D/ack
    fi
done
echo Start: $S mkdir: $F
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The output is following:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;Start: 14:32:12.174908734
  File: `/net/l201u2/mnt/lustre/nfs&apos;
  Size: 4096            Blocks: 8          IO Block: 524288 directory
Device: 1ah/26d Inode: 144115205255725057  Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 14:20:13.000000000 +0400
Modify: 2013-10-05 14:31:24.000000000 +0400
Change: 2013-10-05 14:31:24.000000000 +0400
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The script runs long time and after I executed &quot;ls -la /net/l201u2/mnt/lustre/nfs&quot; in other console finished:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;  File: `/net/l201u2/mnt/lustre/nfs&apos;
  Size: 4096            Blocks: 8          IO Block: 524288 directory
Device: 1ah/26d Inode: 144115205255725057  Links: 4
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 14:20:13.000000000 +0400
Modify: 2013-10-05 14:31:24.000000000 +0400
Change: 2013-10-05 14:31:24.000000000 +0400
mkdir: 14:37:50.287751827
Start: 14:32:12.174908734 mkdir: 14:37:50.287751827
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I observed that &quot;ls&quot; in other console immediately unblock the script and it see new directory that was created on Lustre node. This behavior I observe with patch &lt;a href=&quot;http://review.whamcloud.com/6460&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/6460&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="68444" author="dmiter" created="Sat, 5 Oct 2013 12:24:42 +0000"  >&lt;p&gt;With patch &lt;a href=&quot;http://review.whamcloud.com/6460&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/6460&lt;/a&gt; I observe immediately changes propagation if I read a listing of directory. For example, &quot;while true; do ls; done&quot; on NFS node shows correct listing immediately when I change something on Lustre node.&lt;/p&gt;</comment>
                            <comment id="68454" author="dmiter" created="Sat, 5 Oct 2013 19:10:58 +0000"  >&lt;p&gt;Just to clarify the status. The patch &lt;a href=&quot;http://review.whamcloud.com/6460&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/6460&lt;/a&gt; make situation much better. With this patch readdir fully synchronize directory content and attributes. But only &lt;b&gt;stat&lt;/b&gt; still don&apos;t updates in time. For example:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;# stat /net/l201u2/mnt/lustre/nfs
  File: `/net/l201u2/mnt/lustre/nfs&apos;
  Size: 4096            Blocks: 8          IO Block: 524288 directory
Device: 1bh/27d Inode: 144115205255725057  Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 14:20:13.000000000 +0400
Modify: 2013-10-05 22:55:53.000000000 +0400
Change: 2013-10-05 22:55:53.000000000 +0400
# stat /net/l201u2/mnt/lustre/nfs
  File: `/net/l201u2/mnt/lustre/nfs&apos;
  Size: 4096            Blocks: 8          IO Block: 524288 directory
Device: 1bh/27d Inode: 144115205255725057  Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 14:20:13.000000000 +0400
Modify: 2013-10-05 22:55:53.000000000 +0400
Change: 2013-10-05 22:55:53.000000000 +0400
# ls /net/l201u2/mnt/lustre/nfs
123  234  456  test_ack.sh  test_ask.sh
# stat /net/l201u2/mnt/lustre/nfs
  File: `/net/l201u2/mnt/lustre/nfs&apos;
  Size: 4096            Blocks: 8          IO Block: 524288 directory
Device: 1bh/27d Inode: 144115205255725057  Links: 5
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 14:20:13.000000000 +0400
Modify: 2013-10-05 22:56:59.000000000 +0400
Change: 2013-10-05 22:56:59.000000000 +0400
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;As you can see only &lt;b&gt;ls&lt;/b&gt; command update the &lt;b&gt;stat&lt;/b&gt; information.&lt;/p&gt;</comment>
                            <comment id="68457" author="jhammond" created="Sun, 6 Oct 2013 01:28:58 +0000"  >&lt;p&gt;Thanks Dmitry. There may be more than one issue at play here. There is certainly a spurious negative dentry caching effect on the NFS side. To see this assume /mnt/lustre is exported and mounted via NFS at /mnt/lustre-export and that /mnt/lustre/dir exists but is empty.&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;# cat lu-4050.sh
#!/bin/bash

lustre_dir=/mnt/lustre/dir
export_dir=/mnt/lustre-export/dir

mkdir $lustre_dir/0
stat  $export_dir/1
mkdir $lustre_dir/1
stat  $export_dir/1
# bash -x lu-4050.sh
+ lustre_dir=/mnt/lustre/dir
+ export_dir=/mnt/lustre-export/dir
+ mkdir /mnt/lustre/dir/0
+ stat /mnt/lustre-export/dir/1
stat: cannot stat `/mnt/lustre-export/dir/1&apos;: No such file or directory
+ mkdir /mnt/lustre/dir/1
+ stat /mnt/lustre-export/dir/1
stat: cannot stat `/mnt/lustre-export/dir/1&apos;: No such file or directory
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;The same effect is seen using touch rather than mkdir.&lt;/p&gt;

&lt;p&gt;Dmitry&apos;s two scripts can be simplified to:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;# cat lu-4050-bis.sh
#!/bin/bash

lustre_dir=/mnt/lustre/dir
export_dir=/mnt/lustre-export/dir

stat  $lustre_dir
mkdir $export_dir/0
stat  $export_dir
stat  $export_dir/1
stat  $lustre_dir
mkdir $lustre_dir/1
stat  $lustre_dir
stat  $export_dir/1
stat  $export_dir
# bash -x lu-4050-bis.sh 
+ lustre_dir=/mnt/lustre/dir
+ export_dir=/mnt/lustre-export/dir
+ stat /mnt/lustre/dir
  File: `/mnt/lustre/dir&apos;
  Size: 4096      	Blocks: 8          IO Block: 4096   directory
Device: 2c54f966h/743766374d	Inode: 144115205255725102  Links: 2
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 20:13:23.000000000 -0500
Modify: 2013-10-05 20:13:23.000000000 -0500
Change: 2013-10-05 20:13:23.000000000 -0500
+ mkdir /mnt/lustre-export/dir/0
+ stat /mnt/lustre-export/dir
  File: `/mnt/lustre-export/dir&apos;
  Size: 4096      	Blocks: 8          IO Block: 1048576 directory
Device: 1dh/29d	Inode: 144115205255725102  Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 20:13:23.000000000 -0500
Modify: 2013-10-05 20:13:45.000000000 -0500
Change: 2013-10-05 20:13:45.000000000 -0500
+ stat /mnt/lustre-export/dir/1
stat: cannot stat `/mnt/lustre-export/dir/1&apos;: No such file or directory
+ stat /mnt/lustre/dir
  File: `/mnt/lustre/dir&apos;
  Size: 4096      	Blocks: 8          IO Block: 4096   directory
Device: 2c54f966h/743766374d	Inode: 144115205255725102  Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 20:13:23.000000000 -0500
Modify: 2013-10-05 20:13:45.000000000 -0500
Change: 2013-10-05 20:13:45.000000000 -0500
+ mkdir /mnt/lustre/dir/1
+ stat /mnt/lustre/dir
  File: `/mnt/lustre/dir&apos;
  Size: 4096      	Blocks: 8          IO Block: 4096   directory
Device: 2c54f966h/743766374d	Inode: 144115205255725102  Links: 4
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 20:13:23.000000000 -0500
Modify: 2013-10-05 20:13:45.000000000 -0500
Change: 2013-10-05 20:13:45.000000000 -0500
+ stat /mnt/lustre-export/dir/1
stat: cannot stat `/mnt/lustre-export/dir/1&apos;: No such file or directory
+ stat /mnt/lustre-export/dir
  File: `/mnt/lustre-export/dir&apos;
  Size: 4096      	Blocks: 8          IO Block: 1048576 directory
Device: 1dh/29d	Inode: 144115205255725102  Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2013-10-05 20:13:23.000000000 -0500
Modify: 2013-10-05 20:13:45.000000000 -0500
Change: 2013-10-05 20:13:45.000000000 -0500
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Notice that there is no rmdir in the script and that the link counts reported for the directory are 2, 3, 3, 4, 3.&lt;/p&gt;</comment>
                            <comment id="68471" author="jhammond" created="Mon, 7 Oct 2013 01:34:23 +0000"  >&lt;p&gt;I think this can be explained by the fact that we don&apos;t maintain i_version and we have second resolution timestamps. Thus a nfsd getattr followed by a Lustre mkdir or create in the same second defeats NFS&apos;s change_attr logic.&lt;/p&gt;</comment>
                            <comment id="68472" author="adilger" created="Mon, 7 Oct 2013 04:35:43 +0000"  >&lt;p&gt;I was thinking we &lt;em&gt;could&lt;/em&gt; export the directory version as the Lustre inode version for the directory, but in fact that may not work. The inode version is typically the last transaction number that modified it, which seems reasonable, but to avoid contention in the case of parallel directory operations and version based recovery, I &lt;em&gt;think&lt;/em&gt; that the parent directory version is not updated for every create, just for operations on the directory inode itself.&lt;/p&gt;

&lt;p&gt;Need to ask Mike about this to confirm.&lt;/p&gt;

&lt;p&gt;If I&apos;m wrong then the inode version would be perfect for this. &lt;/p&gt;</comment>
                            <comment id="68731" author="dmiter" created="Thu, 10 Oct 2013 08:48:37 +0000"  >&lt;p&gt;Also patch set #6 of &lt;a href=&quot;http://review.whamcloud.com/#/c/6460/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/6460/&lt;/a&gt; helps with this issue.&lt;/p&gt;</comment>
                            <comment id="68759" author="paf" created="Thu, 10 Oct 2013 19:21:50 +0000"  >&lt;p&gt;Dmitry,&lt;/p&gt;

&lt;p&gt;Can you clarify what you mean by helps?  Does it resolve the issue?  Or if it doesn&apos;t resolve the issue, how exactly does it help?&lt;/p&gt;</comment>
                            <comment id="68813" author="dmiter" created="Fri, 11 Oct 2013 13:38:30 +0000"  >&lt;p&gt;With this patch make directory on NFS share in sync with Lustre if used readdir(). But stat() is not updated if mtime is not changed in terms of seconds. Probably it&apos;s fine but I&apos;d like to investigate what can be done to proper updating stat().&lt;/p&gt;</comment>
                            <comment id="68816" author="jhammond" created="Fri, 11 Oct 2013 14:17:54 +0000"  >&lt;p&gt;Andreas, you&apos;re not wrong. The parent directory is not updated for creates. From looking at this and the NFS side, it seems like nanosecond timestamps are the rightest thing here.&lt;/p&gt;</comment>
                            <comment id="68849" author="pjones" created="Fri, 11 Oct 2013 18:06:14 +0000"  >&lt;p&gt;THis may simply be a duplicate of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3240&quot; title=&quot;The link count is not updated after the mkdir&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3240&quot;&gt;&lt;del&gt;LU-3240&lt;/del&gt;&lt;/a&gt; (now marked as a 2.5.0 blocker) in which case it can be closed as a duplicate of that ticket. If there is still any residual work then it is a lower priority and can be handled in a later release&lt;/p&gt;</comment>
                            <comment id="69452" author="jlevi" created="Mon, 21 Oct 2013 20:56:55 +0000"  >&lt;p&gt;Dmitry,&lt;br/&gt;
Would you open a new ticket for the remaining work that needs to be completed for this? Then close this ticket with a FixVersion of 2.5.0?&lt;br/&gt;
Thank you!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="13394">LU-1158</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="18608">LU-3240</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzw4nb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10863</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>