shared directory only mounts on the command line

English Network/Internet
1

I have a PC with the directory “/home/sergio” shared.
I access this share using the following line from “fstab”


192.168.1.108:/home/pcFatur   /mnt/pc2Fatur     nfs    nofail,users,user,rw      0 0

After an upgrade from 13.1 to 13.2, this partition can be mounted by any user on the command line in a console, but is not mounted with Dolphin by clicking on “/mnt/pc2Fatur”. Also it is not mounted at startup.

How do I solve this problem?

Thanks in advance

2

You can run the following and see what information might be returned

The following displays all errors since your last bootup (ie your current session)

journalctl -p err -b

Or, you can display all your journal messages and scroll through them all looking for possible relevant entries

journalctl -b

You might also click on your ESC key after your GRUB menu selection so that you can see your boot entries until your User login.

I’m going to suspect that maybe you don’t have your network starting on boot, so is unavailable for network connections required by setting up network shares like NFS.

HTH,
TSU

3

BTW
If network availability is the issue, you can also avoid the problem by specifying the mount should occur only on first access (not during boot).

You would do this by passing the “_netdev” option, so your fstab line would read

192.168.1.108:/home/pcFatur   /mnt/pc2Fatur     nfs    nofail,_netdev,users,user,rw      0 0

The result should be that there will be a slight delay on first access when the mount actually is done.

TSU

4

Sorry, but that’s wrong.

“_netdev” will only tell the system that this is a network mount, so it will only be mounted when the network is up, not before.
It will still be mounted during boot though, not at first access.

See “man mount”:

       **_netdev
**              The  filesystem resides on a device that requires network access
              (used to prevent the  system  from  attempting  to  mount  these
              filesystems until the network has been enabled on the system).

It’s still advisable to add “_netdev” though, for obvious reasons. This may even fix the problem…

If you want to mount something on first access, you would need to use e.g. autofs.

5

Thx for the correction,
A re-read does say that mounting is during the boot process,

But, I doubt very much that autofs has anything to do with a delayed mount.
I can’t seem to find the Forum thread which described this command, and it wasn’t that long ago… Maybe within the past 6 months?
Spent about 10 minutes unsuccessfully plugging in search keywords without finding the thread… I remember that at the time this was a neat trick mentioned by another poster in the thread because it’s not mentioned often on the Internet (I commented on this at the time, too).

TSU

6

Of course it has.
The sole purpose of autofs is to mount things on demand, when they are first accessed:

$ rpm -qi autofs
Name        : autofs
Version     : 5.1.0
Release     : 2.8.1
Architecture: x86_64
Install Date: Fre 13 Mär 2015 17:06:22 CET
Group       : System/Daemons
Size        : 3638063
License     : GPL-2.0+
Signature   : RSA/SHA256, Mit 11 Mär 2015 13:05:48 CET, Key ID b88b2fd43dbdc284
Source RPM  : autofs-5.1.0-2.8.1.src.rpm
Build Date  : Die 03 Mär 2015 16:08:46 CET
Build Host  : build17
Relocations : (not relocatable)
Packager    : http://bugs.opensuse.org
Vendor      : openSUSE
URL         : http://www.kernel.org/pub/linux/daemons/autofs/v5/
Summary     : A Kernel-Based Automounter
Description :
AutoFS is a kernel-based automounter for Linux.  It automatically
mounts filesystems when you use them, and unmounts them later when
you are not using them.  This can include network filesystems, CD-ROMs,
floppies, and so forth.
Distribution: openSUSE 13.2
7

The only uses I’ve run into using autofs were use as a generic file system for storing image libraries on the fs of choice.

You may be right that autofs has additional features, I just haven’t seen those personally.
No NFS mounts I’ve run into yet have required an autofs implementation…

TSU

8

Maybe you are thinking of a different “autofs”?

You may be right that autofs has additional features, I just haven’t seen those personally.
No NFS mounts I’ve run into yet have required an autofs implementation…

An NFS mount does not require autofs.

Again, autofs makes it possible to mount filesystems (not only, but also, NFS) automatically when you try to access them (and can unmount them automatically again as well).

9

I’m sure only one “autofs” exists,
And, I can see how autofs was used the times I ran into it could also be of benefit in other, and perhaps for more “main” purposes.
In the cases I ran into it (IIRC might have also been related to early Linux implementations of ZFS in Linux) I can see how maybe someone had a need and saw that a subset of total features might have been perfect to address an issue.

TSU

10

Along with the suggestion to consider using autofs, another is to include the noauto option in the nfs mount entry like this

192.168.1.108:/home/pcFatur   /mnt/pc2Fatur     nfs    nofail,users,user,rw,noauto      0 0

then it won’t be mounted until first needed (accessed).

It should show up on ‘Places’ > ‘Devices’ in Dolphin, and allow you to mount on demand.

That is how I currently access my remote NFS share.

In fact it is also possible to browse remote NFS shares without any /etc/fstab remote share defined. This can be useful when infrequent administrator access is required for example. Dolphin can be launched (as root) with

kdesu dolphin

then do

192.168.1.108:/home/pcFatur