Dolphin taking 10 seconds + to open my home directory

English Applications
1

Dolphin is now taking more than 10 seconds just to open my home directory. Does anybody else have this problem? I cannot find if it is following a recent update or the fact that the NFS server is down.

The machine I am using which has the slow Dolphin start had two NFS clients set up and the delay might be due to autofs timing out looking for the server.

alastair@HP-Z640-1:~> sudo systemctl status home-alastair-NFS_from_ibmserv_134_Mastermedia.automount
[sudo] password for root: 
● home-alastair-NFS_from_ibmserv_134_Mastermedia.automount - nfs automount for 134 /home/alastair/Mastermedia
     Loaded: loaded (/etc/systemd/system/home-alastair-NFS_from_ibmserv_134_Mastermedia.automount; enabled; preset>
     Active: active (waiting) since Thu 2023-12-28 17:29:13 GMT; 18h ago
   Triggers: ● home-alastair-NFS_from_ibmserv_134_Mastermedia.mount
      Where: /home/alastair/NFS_from_ibmserv_134_Mastermedia

Dec 28 22:13:33 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
Dec 28 22:13:38 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
Dec 28 22:13:43 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
Dec 28 22:13:48 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
Dec 28 22:13:53 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
Dec 29 09:31:44 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
Dec 29 11:37:39 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
Dec 29 11:50:51 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
Dec 29 11:51:01 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
Dec 29 12:19:25 HP-Z640-1 systemd[1]: home-alastair-NFS_from_ibmserv_134_Mastermedia.automount: Got automount requ>
lines 1-16/16 (END)

I think the clue is in the (waiting). How do I temporarily turn this off?

2

I should have added I am concerned by the difference between systemctl enable and disable. If I use the specific unit this should disable the command but when I re-boot will the re-enabled?

3

How? No configuration shown whatever shown by you.

What concerns you? The one is the opposite of the other. Switch on… switch off … switch on … switch off … etc. … etc.

1 Like
4

Hi Henk,
I am confused by the info in the manpage:-

Note that
           this removes all symlinks to matching unit files, including manually created symlinks, and not just
           those actually created by enable or link. Note that while disable undoes the effect of enable, the
           two commands are otherwise not symmetric, as disable may remove more symlinks than a prior enable
           invocation of the same unit created.

I have been using the openSUSE reference for On-demand mounting with autofs but have not been able to retrace my steps. I cannot find the excellent example I had used when I set these two NFS shares previously and I have in my /etc/systemd/system/…

-rw-r--r-- 1 root root  176 Nov 27 18:45 home-alastair-NFS_from_ibmserv_134_alastair.automount
-rw-r--r-- 1 root root  227 Nov 27 19:15 home-alastair-NFS_from_ibmserv_134_alastair.mount
-rw-r--r-- 1 root root  191 Dec  2 18:19 home-alastair-NFS_from_ibmserv_134_Mastermedia.automount
-rw-r--r-- 1 root root  256 Dec  2 18:18 home-alastair-NFS_from_ibmserv_134_Mastermedia.mount

I am trying to understand why there are two lines for each nfs mount and also why when I look at /etc/auto.master the only entry is:-

alastair@HP-Z640-1:/etc> cat auto.master
#
# Sample auto.master file
# This is a 'master' automounter map and it has the following format:
# mount-point [map-type[,format]:]map [options]
# For details of the format look at auto.master(5).
#
#/misc  /etc/auto.misc
#
# NOTE: mounts done from a hosts map will be mounted with the
#       "nosuid" and "nodev" options unless the "suid" and "dev"
#       options are explicitly given.
#
#/net   -hosts
#
# Include /etc/auto.master.d/*.autofs
# To add an extra map using this mechanism you will need to add
# two configuration items - one /etc/auto.master.d/extra.autofs file
# (using the same line format as the auto.master file)
# and a separate mount map (e.g. /etc/auto.extra or an auto.extra NIS map)
# that is referred to by the extra.autofs file.
#
#+dir:/etc/auto.master.d
#
# If you have fedfs set up and the related binaries, either
# built as part of autofs or installed from another package,
# uncomment this line to use the fedfs program map to access
# your fedfs mounts.
#/nfs4  /usr/sbin/fedfs-map-nfs4 nobind
#
# Include central master map if it can be found using
# nsswitch sources.
#
# Note that if there are entries for /net or /misc (as
# above) in the included master map any keys that are the
# same will not be seen as the first read key seen takes
# precedence.
#
+auto.master
alastair@HP-Z640-1:/etc>

Sorry I have forgotten what I did. I shall just read on and hope it all comes back to me.
Meanwhile wishing you a very Happy New Year when it comes!
Alastair.

5

You are drawing me into a nightmare of your undocumented past actions. I will try to avoid this for obvious reasons.

I wolll try to go back to your original questions.

Do you really think that anybody can answer this? Nobody will be able to mind-read every person for this experience.

We already have to start guessing here. This NFS server drops down out of the clean air. You did not mention there is one, let alone how it is used. But

  • when you have NFS mounts
  • and when they are configured to “automount” (on access)
  • and when one or more of the mount points are inside “your” (whoever that may be) home directory
  • and when the some process then tries to access things inside that home directory

then one can expect that things go wrong, of course starting with time outs on the mount trial.

To me it is rather logical that when your infrastructure is broken somewhere, then you will experience problems.

6

@Budgie2:

Is there any particular reason why you do not trust the Automount service?

 # systemctl status autofs.service 
● autofs.service - Automounts filesystems on demand
     Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled; vendor preset: disabled)
     Active: active (running) since Fri 2023-12-29 09:35:18 CET; 8h ago
       Docs: man:automount(8)
             man:autofs(5)
    Process: 1920 ExecStart=/usr/sbin/automount $AUTOFS_OPTIONS -p /run/automount.pid (code=exited, status=0/SUCCESS)
   Main PID: 1930 (automount)
      Tasks: 4 (limit: 4915)
     CGroup: /system.slice/autofs.service
             └─ 1930 /usr/sbin/automount -p /run/automount.pid

Dez 29 09:35:18 ??? systemd[1]: Starting Automounts filesystems on demand...
Dez 29 09:35:18 ??? automount[1930]: do_init:131: lookup(yp): map auto.master: Local domain name not set
Dez 29 09:35:18 ??? systemd[1]: Started Automounts filesystems on demand.
 #

Here, the time it takes to Automount and access a QNAP NAS box on this LAN

 > time l /mnt/NAS-Bureau-001/NFS/
insgesamt 24
drwxrwxrwx 5 root     root   4096 12. Mai 2023  ./
drwxr-xr-x 3 root     root      0 29. Dez 17:51 ../
drwxrwx--- 5 xxxxxxxx xxxxxx 4096 11. Okt 2021  xxxxxxxx/
drwxrwx--- 4 yyy      yyyyy  4096 18. Aug 17:35 yyy/

real    0m0,397s
user    0m0,003s
sys     0m0,003s
 > 
 > LANG=C tracepath NAS-Bureau-001.fritz.box
 1?: [LOCALHOST]                        0.015ms pmtu 1492
 1:  NAS-Bureau-001.fritz.box                              0.489ms reached
 1:  NAS-Bureau-001.fritz.box                              0.461ms reached
     Resume: pmtu 1492 hops 1 back 1 
 >

As far as I am concerned, about 400 ms needed to access an unmounted NAS directory is OK for a private LAN … :smiling_imp:

7

Yes, but when he explains that the server is down, it is no wonder it does not function like that.

8

Hi Don,
My problem, I believe, is because I have set the configuration for the automount with a 10 second delay if the connection fails. This was a precaution and is never usually invoked but with my server dead means every time I use Dolphin for example.
I had been musing on how to stop this temporarily while server is down. No big deal but I had lost my notes.
Thanks for the info.

9

Hi Henk,
Yes, in my experience anybody who posts on this thread and has a similar problem will likely echo it. Since it has been a while since others have had a similar problem I thought a new post was merited. It provides me with another piece of data whatever the response.

I rather hoped that showing the output of my command in my first post would demonstrate that an NFS server is involved. Sorry it was not clear but the more customary means to investigate a problem is to ask further questions rather than assert opinions, but each to his own.

10

The further question is to support each and every statement you put in a problem description with prove by computer command and it’s output. And never to assume that any tiny bit of your configuration, setup and environment is well known to the others you ask for help.

1 Like
11

When I started this thread I had been trying to retrace the steps I took to set up the to auto-mounts and had not been able to find the excellent thread which had been posted and I had followed, so had been referring to the openSUSE docs,
On-demand mounting with autofs | Reference | openSUSE Leap 15.5 and in particular para 23.4.

This starts with the explicit command:-
Edit the master map file /etc/auto.master: and goes on to say Add a new entry for the new NFS mount at the end of /etc/auto.master:

What has confused me is that it appears I did not follow these instructions because it appears nothing has been added to the /etc/auto.master file

alastair@HP-Z640-1:~> cat /etc/auto.master
#
# Sample auto.master file
# This is a 'master' automounter map and it has the following format:
# mount-point [map-type[,format]:]map [options]
# For details of the format look at auto.master(5).
#
#/misc  /etc/auto.misc
#
# NOTE: mounts done from a hosts map will be mounted with the
#       "nosuid" and "nodev" options unless the "suid" and "dev"
#       options are explicitly given.
#
#/net   -hosts
#
# Include /etc/auto.master.d/*.autofs
# To add an extra map using this mechanism you will need to add
# two configuration items - one /etc/auto.master.d/extra.autofs file
# (using the same line format as the auto.master file)
# and a separate mount map (e.g. /etc/auto.extra or an auto.extra NIS map)
# that is referred to by the extra.autofs file.
#
#+dir:/etc/auto.master.d
#
# If you have fedfs set up and the related binaries, either
# built as part of autofs or installed from another package,
# uncomment this line to use the fedfs program map to access
# your fedfs mounts.
#/nfs4  /usr/sbin/fedfs-map-nfs4 nobind
#
# Include central master map if it can be found using
# nsswitch sources.
#
# Note that if there are entries for /net or /misc (as
# above) in the included master map any keys that are the
# same will not be seen as the first read key seen takes
# precedence.
#
+auto.master
alastair@HP-Z640-1:~> ls /etc/systemd/system

It seems nothing has been added to this file so I have been trying to understand why. That was all.