Did you check to see if you're experiencing any group upcall errors on the MDS? Have you tried disabling group upcall on the MDS?
Also, when looking at the problematic files with lfs getstripe, have you verified that those objects exist? Any errors about missing objects on the OSTs? Any other errors? On Mon, Mar 13, 2017 at 2:25 PM, Vicker, Darby (JSC-EG311) < [email protected]> wrote: > Yes, we use LDAP on the servers and the clients so all nodes get user info > from the same source. > > > > *From: *Colin Faber <[email protected]> > *Date: *Monday, March 13, 2017 at 2:39 PM > *To: *Darby Vicker <[email protected]> > *Cc: *"Gibbins, Faye" <[email protected]>, Murshid Azman < > [email protected]>, "[email protected]" < > [email protected]> > > *Subject: *Re: [lustre-discuss] Odd file permission help please. Has > lustre corrupted? > > > > Is your authentication system across all of your lustre nodes in sync? > > > > On Mon, Mar 13, 2017 at 9:08 AM, Vicker, Darby (JSC-EG311) < > [email protected]> wrote: > > We have the same thing happening on one of our lustre file system (2.4.3 > servers, 2.9 client). All OST’s are connected so that’s not the problem. > We do use ACL’s so I was hopeful this was the cause for us too. But this > doesn’t seem to be the case – any operation on the problem directory just > gives “stale file handle”. How did you clear the ACL’s – just the “setfacl > -b" command? I don’t see anything in the system logs on the MDS or the > OSS’s when I try to do something with the problem directory. Any other > ideas? > > > > [root@dvicker mirrors]# ls -l > > ls: cannot access cpas: Stale file handle > > drwxr-s--- 5 root g27122 4096 Nov 14 08:31 cev-repo > > d????????? ? ? ? ? ? cpas > > drwxrwxr-x 5 root eg3 4096 Aug 21 2014 sls > > [root@dvicker mirrors]# getfacl cpas > > getfacl: cpas: Stale file handle > > [root@dvicker mirrors]# setfacl -b cpas > > setfacl: cpas: Stale file handle > > [root@dvicker mirrors]# > > > > > > *From: *lustre-discuss <[email protected]> on > behalf of "Gibbins, Faye" <[email protected]> > *Date: *Friday, March 10, 2017 at 4:13 AM > *To: *Murshid Azman <[email protected]>, " > [email protected]" <[email protected]> > > > *Subject: *Re: [lustre-discuss] Odd file permission help please. Has > lustre corrupted? > > > > Hi Azman, > > > > When I run “lctl dl” on the client here’s what I get: > > > > Snip--- > > 0 UP mgc MGC172.23.9.20@tcp 86074c24-8612-13ff-5fd2-f3701bb50072 5 > > 1 UP lov results-clilov-ffff882021fed000 > 051cf9bc-1069-4e7e-faea-9957b1f9c7a4 > 4 > > 2 UP lov tools-clilov-ffff881023c96000 a25d30ee-5b94-94e3-a984-2d2892793d9a > 4 > > 3 UP lmv results-clilmv-ffff882021fed000 > 051cf9bc-1069-4e7e-faea-9957b1f9c7a4 > 4 > > 4 UP lmv tools-clilmv-ffff881023c96000 a25d30ee-5b94-94e3-a984-2d2892793d9a > 4 > > 5 UP mdc results-MDT0000-mdc-ffff882021fed000 > 051cf9bc-1069-4e7e-faea-9957b1f9c7a4 > 5 > > 6 UP mdc tools-MDT0000-mdc-ffff881023c96000 > a25d30ee-5b94-94e3-a984-2d2892793d9a > 5 > > 7 UP osc results-OST0000-osc-ffff882021fed000 > 051cf9bc-1069-4e7e-faea-9957b1f9c7a4 > 5 > > 8 UP osc tools-OST0000-osc-ffff881023c96000 > a25d30ee-5b94-94e3-a984-2d2892793d9a > 5 > > 9 UP osc results-OST0001-osc-ffff882021fed000 > 051cf9bc-1069-4e7e-faea-9957b1f9c7a4 > 5 > > 10 UP osc tools-OST0001-osc-ffff881023c96000 > a25d30ee-5b94-94e3-a984-2d2892793d9a > 5 > > 11 UP osc results-OST0002-osc-ffff882021fed000 > 051cf9bc-1069-4e7e-faea-9957b1f9c7a4 > 5 > > 12 UP osc tools-OST0002-osc-ffff881023c96000 > a25d30ee-5b94-94e3-a984-2d2892793d9a > 5 > > 13 UP lov audiodb-clilov-ffff882023ba3000 b3c8c4c9-4001-3a7c-e857-b52850abde1c > 4 > > 14 UP lmv audiodb-clilmv-ffff882023ba3000 b3c8c4c9-4001-3a7c-e857-b52850abde1c > 4 > > 15 UP mdc audiodb-MDT0000-mdc-ffff882023ba3000 > b3c8c4c9-4001-3a7c-e857-b52850abde1c > 5 > > 16 UP osc audiodb-OST0000-osc-ffff882023ba3000 > b3c8c4c9-4001-3a7c-e857-b52850abde1c > 5 > > 17 UP osc audiodb-OST0001-osc-ffff882023ba3000 > b3c8c4c9-4001-3a7c-e857-b52850abde1c > 5 > > 18 UP osc audiodb-OST0002-osc-ffff882023ba3000 > b3c8c4c9-4001-3a7c-e857-b52850abde1c > 5 > > 19 UP osc audiodb-OST0003-osc-ffff882023ba3000 > b3c8c4c9-4001-3a7c-e857-b52850abde1c > 5 > > 20 UP lov scratch-clilov-ffff8810200e7000 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 4 > > 21 UP lmv scratch-clilmv-ffff8810200e7000 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 4 > > 22 UP osc scratch-OST0000-osc-ffff8810200e7000 > 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 5 > > 23 UP mdc scratch-MDT0000-mdc-ffff8810200e7000 > 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 5 > > 24 UP osc scratch-OST0001-osc-ffff8810200e7000 > 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 5 > > 25 UP osc scratch-OST0002-osc-ffff8810200e7000 > 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 5 > > 26 UP osc scratch-OST0004-osc-ffff8810200e7000 > 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 5 > > 27 UP osc audiodb-OST0005-osc-ffff882023ba3000 > b3c8c4c9-4001-3a7c-e857-b52850abde1c > 5 > > 28 UP osc audiodb-OST0004-osc-ffff882023ba3000 > b3c8c4c9-4001-3a7c-e857-b52850abde1c > 5 > > 29 UP osc scratch-OST0005-osc-ffff8810200e7000 > 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 5 > > 30 UP osc scratch-OST0003-osc-ffff8810200e7000 > 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 5 > > 31 UP osc scratch-OST0006-osc-ffff8810200e7000 > 02a0eda5-bd4b-c2f6-953f-54f0930149e3 > 5 > > Snip--- > > > > With someone else’s help I discovered that this was caused by an ACL > setting on the parent directory and clearing out all the ACL’s fixed it. > > > > Thanks for responding. > > > > Yours > > Faye > > > > *From:* Murshid Azman [mailto:[email protected]] > *Sent:* 10 March 2017 09:22 > *To:* Gibbins, Faye <[email protected]>; > [email protected] > *Subject:* Re: [lustre-discuss] Odd file permission help please. Has > lustre corrupted? > > > > I suspect the OST that hosts the file is not mounted. What does lctl dl > gives you on a client? > > > > Murshid. > > > > On Fri, Mar 10, 2017 at 5:19 PM Gibbins, Faye <[email protected]> > wrote: > > Hi, > > > > One of the directories on my lustre file system is showing up like this > when I do an ‘ls -l’ on its parent directory. > > > > d?????????? ? ? ? ? ? L004.Korean > > > > This is happening on every machine the file system is mounted upon. > > > > Can anyone offer advice on what I should do? > > > > Yours > > Faye Gibbins > > > > Snr SysAdmin, Unix Lead Architect > > Software Systems and Cloud Services > > Cirrus Logic > > 0131 272 7398 > > > > This message and any attachments may contain privileged and confidential > information that is intended solely for the person(s) to whom it is > addressed. If you are not an intended recipient you must not: read; copy; > distribute; discuss; take any action in or make any reliance upon the > contents of this message; nor open or read any attachment. If you have > received this message in error, please notify us as soon as possible on the > following telephone number and destroy this message including any > attachments. Thank you. Cirrus Logic International (UK) Ltd and Cirrus > Logic International Semiconductor Ltd are companies registered in Scotland, > with registered numbers SC089839 and SC495735 respectively. Our registered > office is at 7B Nightingale Way, Quartermile, Edinburgh, EH3 9EG, UK. Tel: +44 > (0)131 272 7000 <+44%20131%20272%207000>. cirrus.com > > _______________________________________________ > lustre-discuss mailing list > [email protected] > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.lustre.org_listinfo.cgi_lustre-2Ddiscuss-2Dlustre.org&d=DwMFaQ&c=O3LcjD-V2Iepl5V0N1424A&r=zYKOt5zq8DxD76qBilrgQKxtITGPmVmWHHVOs6JpkMQ&m=DqIEV0rCNQ-ocxqd1iMlhz2gLmttsgnqpPm72u7HZgc&s=O29C6o1pSQeWGsv98jXzM7ZaEB_1HeHNn43-LncGoAU&e=> > > > _______________________________________________ > lustre-discuss mailing list > [email protected] > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org > > >
_______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
