[Bug 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs

Fri Jun 4 17:31:22 UTC 2021

ubuntu at lp1902891-f:~$ grep node /etc/fstab 
ddstreet at 192.168.122.1:/home/ddstreet /mnt/node fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/ddstreet/.ssh/id_rsa,allow_other,reconnect 0 0
ubuntu at lp1902891-f:~$ dpkg -l systemd|grep systemd
ii  systemd        245.4-4ubuntu3.6 amd64        system and service manager
ubuntu at lp1902891-f:~$ ls -l /mnt/node
ls: cannot open directory '/mnt/node': Too many levels of symbolic links
ubuntu at lp1902891-f:~$ journalctl -b -u mnt-node.mount
-- Logs begin at Fri 2021-06-04 15:01:27 UTC, end at Fri 2021-06-04 17:24:29 UTC. --
Jun 04 17:24:07 lp1902891-f systemd[1]: Mounting /mnt/node...
Jun 04 17:24:07 lp1902891-f mount[1302]: read: Connection reset by peer
Jun 04 17:24:07 lp1902891-f systemd[1]: mnt-node.mount: Mount process exited, code=exited, status=1/FAILURE
Jun 04 17:24:07 lp1902891-f systemd[1]: Mounted /mnt/node.

ubuntu at lp1902891-f:~$ grep node /etc/fstab 
ddstreet at 192.168.122.1:/home/ddstreet /mnt/node fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/ddstreet/.ssh/id_rsa,allow_other,reconnect 0 0
ubuntu at lp1902891-f:~$ dpkg -l systemd|grep systemd
ii  systemd        245.4-4ubuntu3.7 amd64        system and service manager
ubuntu at lp1902891-f:~$ ls -l /mnt/node
ls: cannot open directory '/mnt/node': No such device
ubuntu at lp1902891-f:~$ journalctl -b -u mnt-node.mount
-- Logs begin at Fri 2021-06-04 15:01:27 UTC, end at Fri 2021-06-04 17:30:52 UTC. --
Jun 04 17:30:52 lp1902891-f systemd[1]: Mounting /mnt/node...
Jun 04 17:30:52 lp1902891-f mount[1023]: read: Connection reset by peer
Jun 04 17:30:52 lp1902891-f systemd[1]: mnt-node.mount: Mount process exited, code=exited, status=1/FAILURE
Jun 04 17:30:52 lp1902891-f systemd[1]: mnt-node.mount: Failed with result 'exit-code'.
Jun 04 17:30:52 lp1902891-f systemd[1]: Failed to mount /mnt/node.

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1902891

Title:
  "Too many levels of symbolic links” error when using systemd to mount
  sshfs

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  Won't Fix
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  sshfs mount configured in fstab fails with 'too many levels of
  symbolic links'

  [test case]

  configure a sshfs mount in fstab using a remote system where the local
  user performing the mount (usually, root) does not have the remote
  host ssh key in its known hosts db

  then attempt to access any files under the mount, and check the
  journal

  see original description for more detail

  [regression potential]

  any regression would likely cause systemd-mounted filesystem(s) to
  fail to be correctly mounted

  [scope]

  this is needed for g and earlier

  this is fixed upstream with commit
  2fa0bd7d57863dffda89190a70a83c51bd7d114a which is included in v247, so
  this is fixed in h and later

  [original description]

  I have asked question at askubuntu about "Too many levels of symbolic
  links” error when trying to use systemd to mount sshfs
  (https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic-
  links-error-when-using-systemd)

  I have not got any responses, so I am submitting a bug report. If this
  is not a bug, please advice how to mount sshfs share with systemd.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 16:17:04 2020
  InstallationDate: Installed on 2019-11-03 (367 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81H1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago)
  dmi.bios.date: 08/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8PCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 530S-14ARR
  dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
  dmi.product.family: ideapad 530S-14ARR
  dmi.product.name: 81H1
  dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
  dmi.product.version: Lenovo ideapad 530S-14ARR
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1902891/+subscriptions