[LU-4603] NFS reexport leads to problems of "ls" Created: 09/Feb/14  Updated: 22/May/14  Resolved: 22/May/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.6.0
Fix Version/s: Lustre 2.6.0

Type: Bug Priority: Blocker
Reporter: Li Xi (Inactive) Assignee: Di Wang
Resolution: Fixed Votes: 0
Labels: HB, patch

Issue Links:
Related
is related to LU-4601 Failure on test suite parallel-scale-... Closed
is related to LU-3531 DNE2: striped directory Resolved
is related to LU-4869 rmdir allowed on nonempty striped dir... Resolved
is related to LU-4945 req_capsule_get: Wrong buffer for fi... Closed
Severity: 3
Rank (Obsolete): 12590

 Description   

When "ls" under a NFS directory, following error message showes up.

ls: reading directory .: Too many levels of symbolic links

And what is more, if the dirctory is large, (e.g. has more than 23 files), there will be some files missing when doing "ls".

[root@vm1 nfs]# ls * | wc -l
97
[root@vm1 nfs]# ls -l | wc -l
ls: reading directory .: Too many levels of symbolic links
98
[root@server1 113_nfs]# ls /mnt/lustre/nfs/* | wc -l
100

We've confirmed that these problems is introduced by 4e0c8ae(LU-3531 llite: move dir cache to MDC layer). A patch which fixes these problems will be pushed soon.



 Comments   
Comment by Li Xi (Inactive) [ 09/Feb/14 ]

Following is the patch.
http://review.whamcloud.com/9191

Comment by Peter Jones [ 10/Feb/14 ]

Bobbie

Could you please look after this patch

Thanks

Peter

Comment by Andreas Dilger [ 10/Feb/14 ]

Seems related to LU-4601.

Comment by Peter Jones [ 26/Mar/14 ]

Emoly

Could you please refresh the supplied patch to reflect the review feedback?

Thanks

Peter

Comment by Emoly Liu [ 08/Apr/14 ]

Reassign this to wangdi since he is revising the patch.

Comment by Oleg Drokin [ 19/May/14 ]

Li Xi: I wonder if you tried the revised patch to ensure it still fixes your original report? Can you give it a try please?

Comment by Li Xi (Inactive) [ 20/May/14 ]

Hi Oleg,

I've confirmed that the newest patch set (Patch Set 28) fixes my problem. Thanks for reminding.

Comment by Jodi Levi (Inactive) [ 22/May/14 ]

Patch landed to Master and fix confirmed in last comment. Please reopen if more work is needed in this ticket.

Generated at Sat Feb 10 01:44:13 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.