Open dwrobel opened 3 years ago
Thanks for the report! Confirmed that the storage page currently only looks at /etc/fstab, it does not recognize systemd automount units. Please disregard the warning.
@mvollmer, FYI
Confirmed that the storage page currently only looks at /etc/fstab, it does not recognize systemd automount units.
Yes, and neither does Cockpit recognize *.mount units...
@martinpitt @mvollmer Sorry, I do not want to open another issue, so I will add my comment here about the same problem... It seems that Cockpit also has some problem parsing fstab
since using a quoted UUID also generates the same problem:
LABEL=cloudimg-rootfs / ext4 defaults 0 1
LABEL=UEFI /boot/efi vfat umask=0077 0 1
UUID="20d88a65-1c52-4068-93cb-5f3e362d8b96" /opt auto defaults,noatime 0 2
I used "Mount automatically on boot" only to check what was changed, and Cockpit simply added the same entry again in fstab
without quotes, what causes error messages from systemd-fstab-generator
later...
Same here, adding my case, for example:
cat /etc/fstab
/dev/sdb1 /home/user/disk_repo/ xfs defaults 0 0
/dev/sdc1 /home/user/disk_upload/ xfs defaults 0 0
And NFS exports, too:
cat /etc/exports
/home/user/disk_repo *(rw,sync,no_root_squash,no_all_squash,no_subtree_check,insecure)
/home/user/disk_upload *(rw,sync,no_root_squash,no_all_squash,no_subtree_check,insecure)
And actual mounts:
df -h
/dev/sdb1 350G 74G 277G 22% /home/user/disk_repo
/dev/sdc1 500G 11G 490G 3% /home/user/disk_upload
Cockpit version: 235-1
OS: FedoraServer 33 x86_64
Please help us out by explaining how to reproduce it.
I have machine where the second disk is mounted using
systemd
.automount
service (as it's detachable and might or might not be connected to the system). System and disk is working fine - meaning once attached it gets properly mounted by thesystemd
.automount
service.However,
cockpit
complains about it saying:Screenshot:
Cockpit is also not able to show properly the mountpoint - so it make impression that it's not mounted: