You are not logged in.
Pages: 1
I just checked my "systemctl list-units --full | grep active" while working on another issue, when I saw that I have duplicate mounts for a folder on my local server.
I find these two lines;
mnt-DiskStation-Backups.automount loaded active running mnt-DiskStation-Backups.automountand
mnt-DiskStation-Backups.mount loaded active mounted /mnt/DiskStation/BackupsI'm sure the first one is from my fstab where I set up the automount with this line;
192.168.1.100:/volume1/Backups /mnt/DiskStation/Backups nfs rsize=8192,wsize=8192,noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=1min 0 2But the second mount is probably from some old trial and error when setting up the mounts I need.
How do I properly unmount it so I get permanently rid of it.. I thought I already managed to do this a few weeks ago by doing a lazy unmount for it, but it seems to still be in my systemctl units..?
Last edited by 7thSon (2017-11-10 08:44:26)
Offline
If it persists on reboot, is something under /etc/systemd/ responsible?
However, your fstab entry is configured to not mount the volume on boot. I am not sure, but are you sure that what you're seeing isn't normal? The first looks like the unit triggered by the line in fstab, while the second looks like the unit triggered when you access the device, as a result of the unit triggered by the line in fstab. Nothing you've shown obviously points to anything being mounted twice.
(But, as I say, I don't have any automount devices.)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Did you notice that one is an automount service and the other one an actual mount service?
Try the same query *before* triggering the automount (by accessing the path). Then think about the meaning of the results.
Offline
Did you notice that one is an automount service and the other one an actual mount service?
Try the same query *before* triggering the automount (by accessing the path). Then think about the meaning of the results.
Ah, I get what you're saying, that makes sense. I guess I got fooled by ther fact that earlier I did in fact have duplicate mounts for the folder which were causing som issues.
Thanks a lot ![]()
Offline
Pages: 1