[Solved] fuse: unknown option(s): `-o _netdev,user'

DoXer · 2017-09-23 16:35:39

Hi,
I'm running ARCH sinze 4 weeks and mounted my NAS-Filesystem in fstab like this (from the wiki) and it works since a reboot today.

michael@nas:/mnt/pool/freigabe /media/nas/freigabe  fuse.sshfs noauto,x-systemd.automount,_netdev,user,idmap=user,follow_symlinks,identityfile=/home/michael/.ssh/id_rsa,allow_other,default_permissions,uid=1000,gid=100 0 0

After the reboot the mount ist not working and i get the error

fuse: unknown option(s): `-o _netdev,user'

Looks like something with the last update. For the first I removed both options an mount is working, but I think I need both options.

grep fuse /var/log/pacman.log
[2017-08-27 00:26] [ALPM] installed fuse-common (3.1.1-1)
[2017-08-27 00:26] [ALPM] installed fuse3 (3.1.1-1)
[2017-08-27 13:04] [ALPM] installed fuse2 (2.9.7-3)
[2017-09-18 09:31] [ALPM] upgraded fuse-common (3.1.1-1 -> 3.2.0-1)
[2017-09-18 09:31] [ALPM] upgraded fuse2 (2.9.7-3 -> 2.9.7-4)
[2017-09-18 09:31] [ALPM] upgraded fuse3 (3.1.1-1 -> 3.2.0-1)

How can I fix this? How can I get information about the changes? I looked in manual fuse, fusermount3, but no hints.

Regards
Michael

Last edited by DoXer (2017-10-25 20:23:04)

randomguy · 2017-09-23 19:30:15

Did you try downgrading systemd? This behaviour is strange, as those options shouldn't be passed to the fuse binary like that. I suspect this commit: https://github.com/systemd/systemd/comm … 52cb903bba

DoXer · 2017-09-23 20:21:53

No, I didn't try to downgrade.

Why systemd?

randomguy · 2017-09-23 20:29:45

Systemd parses /etc/fstab and creates unit files for the mounts defined in it. Could you show me the output of systemctl status for the unit file? For me it was named after the mount target, so yours should be:

sudo systemctl status media-nas-freigabe.mount

If it doesn't exist under this exact name, check other *.mount unit files.

I could reproduce your problem on my end, mine shows:

● home-eddi-homessh.mount - /home/eddi/homessh
   Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2017-09-23 21:53:55 CEST; 30min ago
    Where: /home/eddi/homessh
     What: eddi@localhost:/home/eddi
     Docs: man:fstab(5)
           man:systemd-fstab-generator(8)
  Process: 1156 ExecMount=/usr/bin/mount eddi@localhost:/home/eddi /home/eddi/homessh -t fuse.sshfs -o x-systemd.automount,_netdev,user,idmap=user,follow_symlinks,identityfile=/home/michael/.ssh/id_rsa,allow_other,default_permissions,uid=1000,gid=100 (code=exited, status=1/FAILURE)

Running the command (everything after ExecMount=) by hand yields your error:

$ sudo /usr/bin/mount eddi@localhost:/home/eddi /home/eddi/homessh -t fuse.sshfs -o x-systemd.automount,_netdev,user,idmap=user,follow_symlinks,identityfile=/home/michael/.ssh/id_rsa,allow_other,default_permissions,uid=1000,gid=100
fuse: unknown option(s): `-o _netdev,user'

Edit: Better guess for the unit file name...

Last edited by randomguy (2017-09-23 20:33:46)

xganesh · 2017-09-23 21:25:47

Same problem here.
I have downgraded systemd from version "234.11-8" to "233.75-3" and the failure persists.

After doing:

# systemctl status FARAWAYDATA.mount

I get the following:

● FARAWAYDATA.mount - /FARAWAYDATA
Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2017-09-23 17:20:25 EDT; 9s ago
Where: /FARAWAYDATA
What: ele@MyFarAwayHost.boldlygoingnowhere.org:/FARAWAYDATA
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 10935 ExecMount=/usr/bin/mount ele@MyFarAwayHost.boldlygoingnowhere.org:/FARAWAYDATA /FARAWAYDATA -t fuse.sshfs -o reconnect,user,allow_other,x-systemd.automount,_netdev,idmap=user,uid=1000,gid=100,IdentityFile=/home/ele/.ssh/id_rsa,port=7204 (code=exited, status=1/FAILURE)
Sep 23 17:20:25 adria systemd[1]: Mounting /FARAWAYDATA...
Sep 23 17:20:25 adria systemd[1]: FARAWAYDATA.mount: Mount process exited, code=exited status=1
Sep 23 17:20:25 adria systemd[1]: Failed to mount /FARAWAYDATA.
Sep 23 17:20:25 adria systemd[1]: FARAWAYDATA.mount: Unit entered failed state.

randomguy · 2017-09-23 21:48:17

xganesh wrote:

Same problem here.
I have downgraded systemd from version "234.11-8" to "233.75-3" and the failure persists.

The suggested commit is just a guess, I am absolutely not sure.

Also, did you make sure that the unit file is regenerated after the downgrade? To make sure, I would change the mount target path, so a new unit with a new name will be created.

Did those fstab entries work for you both at some point in the past?

V1del · 2017-09-23 22:47:07

This has nothing to do with systemd.

This is the change to the fuse3 API. If fuse tells you it doesn't need these options anymore, it likely doesn't need these options anymore. It will mount with the access rights of the mount point, which is going to be your user.

randomguy · 2017-09-23 22:53:14

Fair enough, but what about '_netdev'? My assumption is that it shouldn't appear in the generated .mount files to begin with.

Edit: _netdev is also totally irrelevant in this case. Systemd correctly adds Wants=network-online.target to the unit files with our without it.

V1del is right, just remove those options.

Last edited by randomguy (2017-09-23 23:26:33)

maxchaos · 2017-09-24 10:09:32

Hi.
I am also experiencing the same issue.

I have several remote filesystems that I mount over sshfs with appropriate entries in /etc/fstab. Normally, I mount these fileystems manually but since my last system update I also get the same error.
I removed these two options from my fstab but then trying to manually mount them as a regular user fails with the following error

 mount: /mnt/remotefs: operation permitted for root only.

This was not an issue before and is probably caused by the removal of option "user" which actually should be filesystem independent (according to mount's man pages anyway).

DoXer · 2017-09-24 11:37:07

randomguy wrote:

Systemd parses /etc/fstab and creates unit files for the mounts defined in it. Could you show me the output of systemctl status for the unit file? For me it was named after the mount target, so yours should be:

This is the entry in fstab now:

michael@nas:/mnt/pool/medien /media/nas/medien  fuse.sshfs noauto,x-systemd.automount,idmap=user,follow_symlinks,identityfile=/home/michael/.ssh/id_rsa,allow_other,default_permissions,uid=1000,gid=100 0 0

sudo systemctl status media-nas-freigabe.mount

gives:

Warning: media-nas-freigabe.mount changed on disk. Run 'systemctl daemon-reload' to reload units.
● media-nas-freigabe.mount - /media/nas/freigabe
   Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
   Active: active (mounted) since Sun 2017-09-24 13:31:19 CEST; 3min 18s ago
    Where: /media/nas/freigabe
     What: michael@nas:/mnt/pool/freigabe
     Docs: man:fstab(5)
           man:systemd-fstab-generator(8)
  Process: 10313 ExecMount=/usr/bin/mount michael@nas:/mnt/pool/freigabe /media/nas/freigabe -t fuse.sshfs -o x-systemd.automount,_netdev,user,idmap=user,follow_symlinks,identityfile=/home/

Buddlespit · 2017-09-24 12:24:42

DoXer wrote:

Warning: media-nas-freigabe.mount changed on disk. Run 'systemctl daemon-reload' to reload units.

DoXer · 2017-09-24 12:58:47

After daemon-reload:

● media-nas-freigabe.mount - /media/nas/freigabe
   Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
   Active: active (mounted) since Sun 2017-09-24 14:57:43 CEST; 2s ago
    Where: /media/nas/freigabe
     What: michael@nas:/mnt/pool/freigabe
     Docs: man:fstab(5)
           man:systemd-fstab-generator(8)

shellback · 2017-09-24 18:37:08

Hi!

I am also experience this issue.

And while removing those old options erases the error, I reaches another since (as maxchaos mentioned) removing of the options users hinders me from mounting since I need to be root for that.

Does anyone have any solution for this one yet?

pvl1 · 2017-09-25 15:20:18

removing _netdev and user fixed the problem for me!
many thanks

bonanza · 2017-09-26 07:49:48

V1del wrote:

This has nothing to do with systemd.
This is the change to the fuse3 API. If fuse tells you it doesn't need these options anymore, it likely doesn't need these options anymore. It will mount with the access rights of the mount point, which is going to be your user.

Thanks for this information!
If I mount it using root (as normal user doesn't work anymore) I get different ownership and permissions:

before mount the permission of the mount point are:
Access: (0755/drwxr-xr-x) Uid: ( 2121/ xx) Gid: ( 2121/ xx)

after mounting via root:
Access: (2770/drwxrws---) Uid: ( 0/ root) Gid: ( 2573/ yy )

where user "yy" is my username on the SSH server.
The used options in fstab are: rw,defaults,noauto,default_permissions,idmap=user,exec,allow_other

Am I doing something wrong?

Last edited by bonanza (2017-09-26 08:02:11)

maxchaos · 2017-09-26 08:47:27

After searching around I found that the previous mount helper, mount.fuse, was recently replaced by a new one, mount.sshfs, which is actually a symlink to the sshfs utility
(see corresponding issue and commit )

Taking a closer look at the sources of mount.fuse, I noticed that certain command-line options, with _netdev and user being among them. were ignored by default,
a feature that is missing from the new helper, which probably causes the issue at hand.

For now, I have submitted an issue on github and waiting for a response.

maxchaos · 2017-09-27 19:12:31

The issue seems to have been resolved on the upstream repository but the corresponding distribution's package has not been updated yet.

Should I report a bug on Arch's bug tracker?

eschwartz · 2017-09-28 00:20:15

If you want to open a bugreport asking for this commit to be backported into the Arch package, that is definitely something you could do.

(That does not necessarily mean the maintainer will agree to backport rather than waiting for a new release. OTOH this is technically a regression which is definitely a rationale to backport it.)

32reg · 2017-09-28 20:10:10

Same issue here. Happened after 2017-09-22 upgrade.

jancici · 2017-09-29 07:14:03

I did get into same trouble here.

I dont know, but for last few issues I had, there was more less systemd involved.

Nikus · 2017-09-29 15:10:27

I need regular users to be able to mount remote ssh folders. I used the user option in fstab to do that.
Removing the user option gives me the following error: operation permitted for root only.
As user option is no longer accepted, what is the equivalent with fuse 3 API?

V1del · 2017-09-29 15:19:34

maxchaos wrote:

For now, I have submitted an issue on github and waiting for a response.

It has been established as a regression in sshfs, that will be fixed resp. has been fixed upstream.

maxchaos · 2017-09-30 11:31:30

I opened a bug report regarding this issue. Now we wait.

Last edited by maxchaos (2017-09-30 11:31:46)

Nicky726 · 2017-09-30 11:46:07

With sshfs downgraded to 3.2.0-2 the user option works, in case you need it working now.

doskoi · 2017-09-30 11:49:14

Why not just remove these options? The next version of sshfs will ignore them anyway.

Arch Linux

#1 2017-09-23 16:35:39

[Solved] fuse: unknown option(s): `-o _netdev,user'

#2 2017-09-23 19:30:15

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#3 2017-09-23 20:21:53

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#4 2017-09-23 20:29:45

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#5 2017-09-23 21:25:47

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#6 2017-09-23 21:48:17

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#7 2017-09-23 22:47:07

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#8 2017-09-23 22:53:14

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#9 2017-09-24 10:09:32

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#10 2017-09-24 11:37:07

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#11 2017-09-24 12:24:42

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#12 2017-09-24 12:58:47

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#13 2017-09-24 18:37:08

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#14 2017-09-25 15:20:18

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#15 2017-09-26 07:49:48

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#16 2017-09-26 08:47:27

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#17 2017-09-27 19:12:31

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#18 2017-09-28 00:20:15

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#19 2017-09-28 20:10:10

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#20 2017-09-29 07:14:03

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#21 2017-09-29 15:10:27

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#22 2017-09-29 15:19:34

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#23 2017-09-30 11:31:30

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#24 2017-09-30 11:46:07

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

#25 2017-09-30 11:49:14

Re: [Solved] fuse: unknown option(s): `-o _netdev,user'

Board footer