4

What could be the reason for this?

4

2 Answers 2

9

To me, this looks like a volume mounted with a "Filesystem in Userspace" (FUSE), which is only visible to the user who mounted it. Other users will see the exact output you get.

An example of a FUSE mount would be sshfs, which I use where I mount it as root. And I get the exact same message when I try to list the contents as a non-root user: (I've shortened the output to only the beginning and end)

am@xb:/var/log$ ls -la
ls: cannot access 'xo': Permission denied
ls: cannot access 'xv': Permission denied
total 5244
drwxrwxr-x  18 root       syslog             4096 Apr 21 04:02 .
drwxr-xr-x  14 root       root               4096 May  8  2020 ..
-rw-r--r--   1 root       root                883 Apr 18 06:54 alternatives.log
-rw-r--r--   1 root       root               4010 Mar 28 06:19 alternatives.log.1
...
...
-rw-rw-r--   1 root       utmp            1020672 Apr 22 09:31 wtmp
-rw-rw-r--   1 root       utmp            1057920 Jul 13  2023 wtmp.1
d??????????  ? ?          ?                     ?            ? xo
d??????????  ? ?          ?                     ?            ? xv
ls: cannot access 'xo': Permission denied
ls: cannot access 'xv': Permission denied
am@xb:/var/log$ 
0
1

I see this on both NFS and SMB mounts, where something has interrupted the network connectivity, but the mounting daemon has not recovered gracefully.

You can umount the share and remount it, assuming the network blip has cleared then it should work immediately.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .