please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NFS share does not mount on
Sorry - those last two comments were meant for bug #1827286.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NFS share does not mount on boot using fstab
To manage notifications about
I did a little more testing and this looks to be specific to /home.
Even mounting over /home (no linking) with autofs results in the same
issue.
All autofs files as well as the list of packages installed have been
attached.
As a side note, having /home as a link is an artifact of some very old b
** Attachment added: "chi.packages"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+attachment/5261278/+files/chi.packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
T
Quick update - switched to autofs as a workaround for this 16.04 issue.
That was fine until I ran 'apt upgrade' today. Now I get the following
error:
root@chi:~# ls -la /vol/home/
ls: cannot access '/vol/home/': Too many levels of symbolic links
root@chi:~#
I'll be opening a new bug for autofs
I should note this is impacting an image built from 16.04.4. Another
image built from 16.04.1 is working fine.
Both have been pulled forward via apt dist-upgrade and their behaviors
differ - concerning in it's own right.
--
You received this bug notification because you are a member of Ubuntu
B
Same issue here. NFS fails to mount at boot, but logging in and issuing
a manual "mount -a" resolves until the next reboot.
It should also be noted that there's a significant delay on boot with
nfs entries in fstab - need to time it, but ~1 minute.
Why issues with something as old/stable/boring
This is affecting me as well but oddly not all hosts. One host will be
problematic for a while then it will shift to another.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NFS share
I have the same issue - installed version of 18.04 today and none of my
NFS mounts happen at boot.
May 30 17:23:41 can-srv systemd[1]: mnt-docker.mount: Directory /mnt/docker to
mount over is not empty, mounting anyway.
May 30 17:23:41 can-srv systemd[1]: Mounting /mnt/docker...
May 30 17:23:41 c
I am experiencing the exact same issue with a fresh install of Ubuntu
18.04. Five other machines on the same network with the same NFS mount
are not experiencing the issue. Three are 18.04 but were upgraded from
14.04 or 16.04 and the other two are on 16.04 and were upgraded from
12.04 and will soo
This bug reappeared (with cifs/smb mounts in fstab) after upgrade to
17.10 "artful" for me. The fix in #5 worked just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NFS share doe
I have similar problems with a cifs/smb mount sometimes.
Can not reliable reproduce this, but maybe adding lines to
/lib/systemd/system/remote-fs-pre.target
helps:
Wants=network-online.target
After=network-online.target
like stated here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1
Have been plagued with this for a while now, noted that Debian tracked a
similar issue (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746358)
but the solution/scripting is different for ubuntu but could this be
ported? Problem presents on every boot, I use the linux-bridge package
to create a
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NFS share does not mount on boot using fstab
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NF
I just noticed the shutdown part of my bug description is not true
(anymore). Maybe I got things mixed up or something changed during the
last week. Anyway, the boot problem is alive and well.
** Summary changed:
- NFS share does not mount on boot using fstab and does not unmount if mounted
manu
16 matches
Mail list logo
