Bug 17357

Summary: systemd-227 looks for not exiting target: "nfs.target"
Product: Mageia Reporter: Piotr Mierzwinski <piotr.mierzwinski>
Component: RPM PackagesAssignee: Guillaume Rousse <guillomovitch>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: systemd-227-2.mga6, nfs-utils-1.3.3-1.mga6 CVE:
Status comment:

Description Piotr Mierzwinski 2015-12-18 03:59:16 CET 
Description of problem:
Running below command. In logs I found following:
# dmesg | grep nfs
[    7.062862] systemd[1]: nfs.target: Cannot add dependency job, ignoring: Unit nfs.target failed to load: No such file or directory.
[   94.686647] kernel: FS-Cache: Netfs 'nfs' registered for caching

Version-Release number of selected component (if applicable):
systemd-227-2.mga6, nfs-utils-1.3.3-1.mga6


By the way.
I'm not sure is this the reason that I'm not able to mount nfs resources with such settings and using nfs v4.

mount host:/path/to/resource         /mount/point nfs rsize=8192,wsize=8192,timeo=14,intr,nosuid
mount.nfs: an incorrect mount option was specified

but I'm able to mount when I use nfs ver3 (adding following parameter nfsvers=3)

# lsmod | grep nfs
nfsv4                 323584  0
nfs                   241664  1 nfsv4
lockd                  90112  1 nfs
fscache                81920  2 nfs,nfsv4
sunrpc                311296  4 nfs,lockd,nfsv4
# ps -ef | grep nfs |grep -v grep
root      1515     2  0 gru17 ?        00:00:00 [nfsiod]


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-12-18 20:03:29 CET 
About systemd: when the current version of nfs-utils was committed, the maintainer mentioned:

guillomovitch <guillomovitch> 1:1.3.3-1.mga6:
+ Revision: 907835
- new version 1.3.3
- sync with upstream systemd units (may need further update work...)

For the rest, I don't know whether your problem is actually the same one as Frank Griffin reported in bug 17326 (even if he uncommented "Defaultvers=4", while you added "nfsvers=3").

Anyway, Guillomovitch will know, assigning to him :-)

CC: (none) => marja11
Assignee: bugsquad => guillomovitch

Comment 2 Guillaume Rousse 2015-12-22 20:43:18 CET 
The systemd unit name issue (nfs.target vs nfs-client.target) is fixed in nfs-utils-1.3.3-2.mga6.
The protocol version issue is unrelated.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 3 Piotr Mierzwinski 2015-12-22 22:58:21 CET 
I have installed new nfs-utils, restarted system and performed the test. Below please find results:

# dmesg | grep nfs
[    2.973809] systemd[1]: nfs.target: Cannot add dependency job, ignoring: Unit nfs.target failed to load: No such file or directory.
[   13.834214] FS-Cache: Netfs 'nfs' registered for caching

# rpm -qa|grep nfs-utils
nfs-utils-1.3.3-2.mga6

# rpm -qa|grep systemd
systemd-units-227-3.mga6
lib64systemd0-227-3.mga6
systemd-227-3.mga6

# uname -srmv
Linux 4.3.2-desktop-2.mga6 #1 SMP Sat Dec 12 22:47:32 UTC 2015 x86_64

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 4 Guillaume Rousse 2015-12-28 20:15:54 CET 
I can't reproduce the problem. You're likely to have another unit file trying to load not-existing-anymore 'nfs.target' unit, or a dangling symlink in your /etc/systemd directory.
Comment 5 Piotr Mierzwinski 2015-12-29 18:57:30 CET 
OK. I found dangling symlink in /etc/systemd directory :).
After restart I can't see any error when I'm doing dmesg|grep nfs
Thanks for help.

Unfortunately still I can't mount nfs resources (using nfs ver.4) :(
Even I use only one parameter "nfs" in /etc/fstab or in command:

# mount -t nfs host:/path/to/resource /mount/point
mount.nfs: an incorrect mount option was specified

I tested it in different distributions (Kubuntu 15.10 and KaOS 2015.11) and all there was fine. Differences were in systemd version. In KaOS there is using version 228 and in Kubuntu the most likely 224.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Piotr Mierzwinski 2015-12-29 18:57:39 CET

Hardware: i586 => x86_64