In the kernel
$ git log -p v4.4...v4.15 -- fs/autofs4
has a bunch of fixes, but none is clearly matching the case here just by
reading it.
Therefore I'll leave that evaluation to the kernel Team.
@Jason I hope that you can just use HWE kernels and be happy for now
since those seem to work for yo
Debugging per [1], did not show anything new.
There just is no activity on the actual access of /home all I see is the
trigger for /home registering at startup.
Startup:
ubuntu@xenial-autofs-client:/$ sudo automount -f -v --debug
Starting automounter version 5.1.1, master map /etc/auto.master
usi
I played a bit with my config and found:
- the error is even reported if /home is set to mount something that won't work
(e.g. non existent server), so it must failing early in the autofs processing
- one can mount things manually (as expected)
The difference is only 5.1.1-1ubuntu3 to 5.1.2-1ubun
Yep, here we go.
Setting up the same on Xenial got me:
ubuntu@xenial-autofs-client:/$ ll /home
ls: cannot open directory '/home': Too many levels of symbolic links
Very interesting
** Changed in: autofs5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you
Hi Jason,
I understand your comment #12 that we can eliminate the symlink from the
equation.
It is not needed for you to trigger the issue - thanks for that hint.
The only differences between my try to reproduce in comment #3 and yours are:
- you set more NFS options in the master file
- you use
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/autofs5/+bug/1827286/+attachment/5261280/+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/1827286
Tit
** Attachment added: "auto.master"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261274/+files/auto.master
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title
** Attachment added: "auto.direct1"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261267/+files/auto.direct1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Tit
** Attachment added: "auto.net"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261269/+files/auto.net
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
au
** Attachment added: "auto.misc"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261271/+files/auto.misc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
** Attachment added: "auto.smb"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261268/+files/auto.smb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
au
** Attachment added: "autofs.conf"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261266/+files/autofs.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title
** Attachment added: "master.d_direct1.autofs"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261265/+files/master.d_direct1.autofs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I followed the first hits that I have found [1][2] to set up a similar
situation.
After mounting NFS the first time I moved all in my ~ to /vol/home
mount:
192.168.122.247:/mnt/sharedfolder on /vol/home type nfs4
(rw,relatime,vers=4.2,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,r
to summarize and be sure on the case:
1. there is a NFS target
2. you have autofs configured to mount /vol/home from that NFS
3. if there is a symlink /home -> /vol/home before that mount happens it fails
Is the above correct?
--
You received this bug notification because you are a member of Ubun
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
autofs - "Too many levels of symbolic links" after apt upgrade
To manage notifications about this bug go to:
http
18 matches
Mail list logo
