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 Buterbaugh - Senior System Administrator
Vanderbilt University - Advanced Computing Center for Research and Education
On Feb 14, 2018, at 12:38 PM, Simon Thompson (IT Research Support)
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.
on behalf of john.hea...@asml.com<mailto:john.hea...@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
We often see this behavior on a GPFS filesystem.
I log into a client.
[jhearns@pn715 test]$ ls -la ../
ls: cannot access ../..: Permission denied
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
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
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org<http://spectrumscale.org>
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org