https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-1550 Lustre <p>getdents() on lustre client mount returns inconsistent/bad data. According to stat(), the /mnt/lustre inode has ino 0x61ab:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@r62-lustre lustre]# sys_stat -x /mnt/lustre dev 2c54f966 ino 61ab mode 41ed nlink 3 uid 0 gid 0 rdev 0 size 1000 blksize 1000 blocks 8 atime 4fe3593b mtime 4fe363e7 ctime 4fe363e7 </pre> </div></div> <p>While according to getdents() it does not. Instead we get the ino based on its <br/> FID. (Note that the output of `ls -ai /mnt/lustre' is not based<br/> entirely on the output of getdents().)</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@r62-lustre lustre]# sys_getdents -x /mnt/lustre d 61ac `.lustre' d 20000000100000d `..' d 200000001000006 `.' </pre> </div></div> <p>Also for a mount point shouldn't the entries for '.' and '..' have the same d_ino?</p> <p>Calling path2fid on /mnt/lustre returns <span class="error">&#91;0x61ab:0xc04ebc0f:0x0&#93;</span>, and<br/> accessing /mnt/lustre thereby seems OK. However the FID derived from<br/> the d_ino for '.' in /mnt/lustre offers a cache-incoherent view on<br/> that directory:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre># cd /mnt/lustre [root]# stat . File: `.' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 2c54f966h/743766374d Inode: 25003 Links: 3 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2012-06-21 12:26:19.000000000 -0500 Modify: 2012-06-21 13:11:51.000000000 -0500 Change: 2012-06-21 13:11:51.000000000 -0500 [root]# stat .lustre/fid/[0x200000001:0x6:0x0] File: `.lustre/fid/[0x200000001:0x6:0x0]' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 2c54f966h/743766374d Inode: 144115188092633094 Links: 3 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2012-06-21 13:39:08.000000000 -0500 Modify: 2012-06-21 13:39:19.000000000 -0500 Change: 2012-06-21 13:39:19.000000000 -0500 [root]# cd /mnt/lustre [root]# ls -a . .. .lustre [root]# ls -a .lustre/fid/[0x200000001:0x6:0x0] . .. .lustre [root]# touch FOO [root]# ls -a . .. FOO .lustre [root]# ls -a .lustre/fid/[0x200000001:0x6:0x0] . .. .lustre [root]# touch .lustre/fid/[0x200000001:0x6:0x0]/BAR [root]# ls -a . .. FOO .lustre [root]# ls -a .lustre/fid/[0x200000001:0x6:0x0] . .. BAR FOO .lustre [root]# touch BAZ [root]# ls -a . .. BAR BAZ FOO .lustre [root]# ls -a .lustre/fid/[0x200000001:0x6:0x0] . .. BAR FOO .lustre </pre> </div></div> # cat /proc/fs/lustre/version <br/> lustre: 2.2.55<br/> kernel: patchless_client<br/> build: 2.2.55-gef32640-CHANGED-2.6.32-220.13.1.el6.l22.x86_64 LU-1550

open-by-fid getdents may return inconsistend data

Bug Minor Resolved Fixed WC Triage John Hammond fid readdir Thu, 21 Jun 2012 15:01:29 +0000 Tue, 29 Apr 2014 22:07:51 +0000 Tue, 5 Feb 2013 18:08:00 +0000 Lustre 2.3.0 Lustre 2.1.2 0 5 <p>This is the same issue as I reported in <a href="https://jira.whamcloud.com/browse/LU-838" title="&quot;lfs path2fid /mnt/lustre&quot; (ROOT) returns inode number" class="issue-link" data-issue-key="LU-838"><del>LU-838</del></a>, but this one has much better detail.</p> <p>These bugs are symptoms that internal files should not be accessible through .lustre.</p> <p>Ned, is this still the case with a 2.4 filesystem? I'd hope that the changes under <a href="https://jira.whamcloud.com/browse/LU-838" title="&quot;lfs path2fid /mnt/lustre&quot; (ROOT) returns inode number" class="issue-link" data-issue-key="LU-838"><del>LU-838</del></a> and LFSCK would have fixed this problem.</p> <p>Andreas, no I don't have any first hand knowledge of this bug.</p> <p>I added the "dotlustre" label to several Jira issues that discuss the ".lustre" directory, purely for my own research purposes (hope that's OK). I'm trying to piece together what this mysterious directory is for and what interfaces it supports. If it is documented somewhere I haven't been able to find it. It seems "open by fid" is the primary (only?) interface for now. It would be great if the Lustre manual contained some explanation, particularly since it shows up in the user-visible namespace, but that's an issue for LUDOC.</p> Duplicate LU-838 Related LU-1518 Development Rank 1|hzvoin: Rank (Obsolete) 7793 Severity