x-systemd.automount causes high load

kodiak · 2015-05-12 10:06:50

Following entry in my fstab causes high load (>2.0) and network traffic to machine (>200Kb via iftop) right after login into a XFCE sessions and keeps like that:

kodiak@machine/ /home/kodiak/mnt/machine fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/kodiak/.ssh/id_rsa,allow_other,reconnect,exec,transform_symlinks,comment=x-gvfs-show 0 0

mount does not list the filesystem, so it is even not mounted.

If I remove the option x-systemd.automount load and traffic keeps low before and after mounting the file system by hand. Did somebody else observer a similar behavior? Is it a bug?

Last edited by kodiak (2015-05-20 15:21:39)

Soukyuu · 2015-05-12 11:07:00

I have a similarly mounted sshfs entry with systemd.automount and I'm not seeing any load or network traffic that I'm not causing.
I don't know if you have to specify the cipher when mounting sshfs, but I did:

root@zacate:/var/cache/pacman/pkg        /mnt/pkgcache           fuse.sshfs      noauto,x-systemd.automount,idmap=user,port=12345,_netdev,identityfile=/root/.ssh/id_rsa,allow_other,default_permissions,uid=0,gid=0,umask=0,reconnect,cache=yes,kernel_cache,ciphers=arcfour256,compression=no

When I'm downloading stuff with pacman, I get pretty high traffic both down and up. It also mounts fine by itself.

Please note that the ciphers I'm using have been deemed insecure, but I'm accessing this share over local network only and access from the outside is blocked, so I prioritized speed over security.

kodiak · 2015-05-12 12:41:28

Thanks Soukyuu, I tried the following:

kodiak@machine:/  /home/kodiak/mnt/machine fuse.sshfs noauto,users,x-systemd.automount,idmap=user,_netdev,IdentityFile=/home/kodiak/.ssh/id_rsa,allow_other,default_permissions,reconnect,cache=yes,kernel_cache,ciphers=arcfour256,compression=no

with no difference.

Soukyuu · 2015-05-12 18:37:10

I should have been more clear, sorry. You can't use cipher=arcfour256 with default configuration because it was removed, take a look at /etc/ssh/ssh_config for the ciphers that are used per default. You can use one of those, or add arcfour256 to it. As far as I know, if you change/add ciphers, you have to do it on both the server and the client, and restart the sshd.service on the server machine after that.

Also, take a look at the SSH wiki article.

kodiak · 2015-05-20 14:10:25

Hi Soukyuu,
I have not touched any of the ciphers, neither on client nor on server. I figured out that thunar shows volumes now, regardless of x-systemd.automount being used or not, so I can drop that. Still leaves the question what caused the traffic, but I is not important for me right now. Thanks for your help!

ewaller · 2015-05-20 14:36:09

Please to not use [CLOSED] in the thread title. Closed has the reserved meaning that a moderator has locked the thread. That is not the case -- this thread is still open.

Arch Linux

#1 2015-05-12 10:06:50

x-systemd.automount causes high load

#2 2015-05-12 11:07:00

Re: x-systemd.automount causes high load

#3 2015-05-12 12:41:28

Re: x-systemd.automount causes high load

#4 2015-05-12 18:37:10

Re: x-systemd.automount causes high load

#5 2015-05-20 14:10:25

Re: x-systemd.automount causes high load

#6 2015-05-20 14:36:09

Re: x-systemd.automount causes high load

Board footer