Sorry - those last two comments were meant for bug #1827286.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NFS share does not mount on boot using fstab
St
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.l
Looks like the issue is symlinking to a director prior to autofs
mounting it.
Everything fine...
root@numbersix:/# ssh chi uname -a
Linux chi 4.4.0-146-generic #172-Ubuntu SMP Wed Apr 3 09:00:08 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
root@chi:~# ls -la /home
ls: cannot access '/home': No such f
** Tags added: autofs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
autofs - "Too many levels of symbolic links" after apt upgrade
Status in systemd pack
Public bug reported:
Description:Ubuntu 16.04.6 LTS
Release:16.04
I moved to autofs this week as a workaround for Bug #1577575 failing to
mount NFS entries at boot. This worked file until I ran 'apt upgrade'
today.
Now trying to access /vol/home mount results in the following error:
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
T
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
9 matches
Mail list logo
