Hi,

I am running KDE neon User Edition 5.18 with some mount points inside /mnt, kernel says /mnt/trash is mounted, but bash says otherwise. Has anyone seen this, what's going on?

Code: Select all

root@Matrix:~# cat /etc/lsb-release
DISTRIB_ID=neon
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="KDE neon User Edition 5.18"
root@Matrix:~# mount | grep trash
/dev/sdc1 on /mnt/trash type fuseblk (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
root@Matrix:~# df -h
Sist. Arq.      Tam. Usado Disp. Uso% Montado em
udev            7,8G     0  7,8G   0% /dev
tmpfs           1,6G  1,6M  1,6G   1% /run
/dev/sdb2       116G  7,0G  104G   7% /
tmpfs           7,8G  518M  7,3G   7% /dev/shm
tmpfs           5,0M  4,0K  5,0M   1% /run/lock
tmpfs           7,8G     0  7,8G   0% /sys/fs/cgroup
/dev/sda2        96M   31M   66M  32% /boot/efi
/dev/sdc3        37G   49M   35G   1% /tmp
/dev/sdc6       165G   80G   77G  52% /home
/dev/sdc5        40G  2,6G   35G   7% /var
/dev/loop1       28M   28M     0 100% /snap/snapd/6953
/dev/loop4       25M   25M     0 100% /snap/snapd/6434
/dev/loop0      129M  129M     0 100% /snap/sweethome3d-homedesign/9
/dev/loop2      1,8M  1,8M     0 100% /snap/bing-wall/9
/dev/loop3       45M   45M     0 100% /snap/gtk-common-themes/1440
/dev/loop6       49M   49M     0 100% /snap/gtk-common-themes/1474
/dev/loop5      172M  172M     0 100% /snap/qt551/27
/dev/loop8      164M  164M     0 100% /snap/spotify/41
/dev/loop7       55M   55M     0 100% /snap/core18/1705
/dev/loop9       55M   55M     0 100% /snap/core18/1668
tmpfs           1,6G     0  1,6G   0% /run/user/0
tmpfs           1,6G   44K  1,6G   1% /run/user/1000
root@Matrix:~# grep trash /etc/fstab
# /mnt/trash was on /dev/sdc1 during installation
UUID=489BF1D01FF7F25B /mnt/trash      ntfs    defaults,umask=007,gid=46 0       0
root@Matrix:~# blkid /dev/sdc1
/dev/sdc1: LABEL="trash" UUID="489BF1D01FF7F25B" TYPE="ntfs" PTTYPE="dos" PARTUUID="84fc6102-01"
root@Matrix:~# cd /mnt
root@Matrix:/mnt# ls -la
total 4
drwxr-xr-x  2 root root    0 abr  2 16:57 .
drwxr-xr-x 24 root root 4096 abr  2 16:59 ..
root@Matrix:/mnt# mkdir foo
mkdir: não foi possível criar o diretório “foo”: Permissão negada
root@Matrix:/mnt#


Is that apocalypse already?
I had give a try on autofs couple of days ago, with a nfs on /mn/csc mount point for testing purposes only, could that be related?

Tks!

Digging into it I found out that when I pointed autofs to use /mnt it changed the folder type to 'autofs', while it should be 'ext2/ext3":

Code: Select all

root@Matrix:~# stat -f /mnt
  Arquivo: "/mnt"
     ID: 0        Comprimento nome: 255     Tipo: autofs
Tamanho de bloco: 4096       Tamanho fundamental de bloco: 4096
 Blocos: Total: 0          Livres: 0          Disponíveis: 0
 Inodes: Total: 0          Livres: 0
root@Matrix:~#

Now, how to revert it back?

I eventually found this kernel doc but no tool or command to revert /mnt type from 'autofs' to 'ext..'. After purging autofs, removed old config files pointing to /mnt, reinstalled and run autofs with its defaults, seem /mnt got its autofs tag removed, and now the issue is fixed, I have my /mnt back.

https://www.kernel.org/doc/html/latest/ ... utofs.html

Went into chmod, tune2fs, parted and fdisk but none seem able to help on this issue. Curious about how could I change that 'mount trap' type flag on a dir without the workaround.
Tks anyway, sorry for the noise and for the sake of future googlers.