[gpfsug-discuss] Odd d????????? permissions

[John Hearns]

Simon, Kevin

Thankyou for your responses.

Simon, indeed we do see this behavior on AFM filesets which have an ‘old’ view – and we can watch the AFM fileset change as the information is updated.

In this case, this filesystem is not involved with AFM.
I Changed the locking semantics from NFSv4 to Posix and the report is that this has solved the problem.


From: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Buterbaugh, Kevin L
Sent: Wednesday, February 14, 2018 9:54 PM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] Odd d????????? permissions

Hi John,

We had a similar incident happen just a week or so ago here, although in our case it was that certain files within a directory showed up with the question marks, while others didn’t.

The problem was simply that the node had been run out of RAM and the GPFS daemon couldn’t allocate memory.  Killing the offending process(es) and restarting GPFS fixed the issue.

We saw hundreds of messages like:

2018-02-07_16:35:13.267-0600: [E] Failed to allocate 92274688 bytes in memory pool, err -1

In the GPFS log when this was happening.  HTHAL…

Kevin

—
Kevin Buterbaugh - Senior System Administrator
Vanderbilt University - Advanced Computing Center for Research and Education
Kevin.Buterbaugh at vanderbilt.edu<mailto:Kevin.Buterbaugh at vanderbilt.edu> - (615)875-9633



On Feb 14, 2018, at 12:38 PM, Simon Thompson (IT Research Support) <S.J.Thompson at bham.ac.uk<mailto:S.J.Thompson at bham.ac.uk>> wrote:

Is it an AFM cache? We see this sort of behaviour occasionally where the cache has an "old" view of the directory. Doing an ls, it evidently goes back to home but by then you already have weird stuff. The next ls is usually fine.

Simon
________________________________________
From: gpfsug-discuss-bounces at spectrumscale.org<mailto:gpfsug-discuss-bounces at spectrumscale.org> [gpfsug-discuss-bounces at spectrumscale.org<mailto:gpfsug-discuss-bounces at spectrumscale.org>] on behalf of john.hearns at asml.com<mailto:john.hearns at asml.com> [john.hearns at asml.com<mailto:john.hearns at asml.com>]
Sent: 14 February 2018 09:00
To: gpfsug main discussion list
Subject: [gpfsug-discuss] Odd d????????? permissions

I am sure this is a known behavior and I am going to feel very foolish in a few minutes…

We often see this behavior on a GPFS filesystem.
I log into a client.

[jhearns at pn715 test]$ ls -la ../
ls: cannot access ../..: Permission denied
total 160
drwx------ 4 jhearns root   4096 Feb 14 09:46 .
d????????? ? ?       ?         ?            ? ..
drwxr-xr-x 2 jhearns users  4096 Feb  9 11:13 gpfsperf
-rw-r--r-- 1 jhearns users 27336 Feb  9 22:24 iozone.out
-rw-r--r-- 1 jhearns users  6083 Feb  9 10:55 IozoneResults.py
-rw-r--r-- 1 jhearns users 22959 Feb  9 11:17 iozone.txt
-rw-r--r-- 1 jhearns users  2977 Feb  9 10:55 iozone.txtvi
-rwxr-xr-x 1 jhearns users   102 Feb  9 10:55 run-iozone.sh
drwxr-xr-x 2 jhearns users  4096 Feb 14 09:46 test
-r-x------ 1 jhearns users 51504 Feb  9 11:02 tsqosperf

This behavior changes after a certain number of minutes, and the .. directory looks normal.

For information this filesystem has nfsv4 file locking semantics and ACL semantics set to all

-- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. Neither the sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt.
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fspectrumscale.org&data=01%7C01%7Cjohn.hearns%40asml.com%7C3b04bafdd99d48fb4b8008d573ed1bf8%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=b7aBB656yJB0E9w%2FiW%2B%2FPSVxP%2BBdDd%2BYfja8NB9geJc%3D&reserved=0>
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgpfsug.org%2Fmailman%2Flistinfo%2Fgpfsug-discuss&data=02%7C01%7CKevin.Buterbaugh%40vanderbilt.edu%7C9df4b4d88544447ac29608d573da2d51%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C1%7C636542303262503651&sdata=v6pnBIEvu6lyP3mGkkRX7hSj58H8vvkUl6R%2FCsq6gmc%3D&reserved=0

-- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. Neither the sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180215/214e4f1b/attachment-0002.htm>