2

Joplin desktop app (https://joplin.cozic.net/) creates a directory in /tmp that I cannot get any info about as root:

While logged in as a regular user I can enter a dir, I cannot even display its attributes:

regularuser@homehost /tmp % ls -ld .mount_JoplinHNsadS
drwxrwxr-x 4 root root 0 Sep 30 21:48 .mount_JoplinHNsadS

regularuser@homehost /tmp % lsattr .mount_JoplinHNsadS
lsattr: Function not implemented While reading flags on .mount_JoplinHNsadS/AppRun
lsattr: Inappropriate ioctl for device While reading flags on .mount_JoplinHNsadS/app
lsattr: Function not implemented While reading flags on .mount_JoplinHNsadS/joplin.desktop
lsattr: Operation not supported While reading flags on .mount_JoplinHNsadS/joplin.png
lsattr: Inappropriate ioctl for device While reading flags on .mount_JoplinHNsadS/usr

However, root cannot even enter this directory:

root@homehost /tmp % ls -al | grep mount
ls: cannot access '.mount_JoplinHNsadS': Permission denied
d?????????  ? ?    ?         ?            ? .mount_JoplinHNsadS

root@homehost /tmp % file .mount_JoplinHNsadS
.mount_JoplinHNsadS: cannot open `.mount_JoplinHNsadS' (Permission denied)

Why is that happening? I thought root can access any directory, even with sticky bit set like /tmp?

How to diagnose such a directory as root? How was this directory created?

Improve this question
2
  • sudo ls -al | grep mount
    – Ra_
    Nov 16, 2018 at 14:00
  • 2
    There is probably a (virtual?) filesystem mounted there. Check the output of mount.
    – Michael Hampton
    Nov 16, 2018 at 15:24

1 Answer 1

Reset to default
0

Thanks to Michael Hampton:

% mount | fgrep .mount
Joplin-1.0.111-x86_64.AppImage on /tmp/.mount_JoplinHNsadS type fuse.Joplin-1.0.111-x86_64.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=1000)
Improve this answer

You must log in to answer this question.

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