linux-kernel - nfs mount fails on startup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <342091379491489@web28m.yandex.ru>
Date:	Wed, 18 Sep 2013 12:04:49 +0400
From:	DimanNe <dimanne@...ru>
To:	linux-kernel@...r.kernel.org
Subject: nfs mount fails on startup

Hello!

After updating to Kubuntu 13.10 beta (kernel version is 3.11.0-7-generic) my nfs share stopped auto-mounting during boot.

Here is my fstab:
dimanne@...edance:~$ cat /etc/fstab
# <file system>                           <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=328a9124-e5ff-4c13-a7e2-559ee6a20292 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=b3a4a4a4-c563-45c1-9d6b-602b07d66c70 none            swap    sw              0       0
# was on /dev/sdb1
UUID=9383ee42-aea8-4098-9533-08d1b9b04e59 /mnt/backup    ext4   defaults        0       2
# was on /dev/sdc1
UUID=4ad4e84a-1e0e-4cb6-a63a-753d3ffc9ff2 /mnt/freedata ext4    defaults        0       2

server:/mnt/media                       /mnt/media      nfs4    defaults


Also I noticed suspicious messages in dmesg:
dimanne@...edance:~$ dmesg | grep killed
[   23.436063] init: idmapd-mounting (/mnt/media) main process (455) killed by TERM signal
[   26.828198] init: failsafe main process (1119) killed by TERM signal
[   28.352642] init: kdm main process (1757) killed by TERM signal

However if I mount nfs share manually (sudo mount -vvv server:/mnt/media /mnt/media) all works perfectly, but at this time I get these messages in dmesg
[  458.804009] NFS: Registering the id_resolver key type
[  458.804024] Key type id_resolver registered
[  458.804026] Key type id_legacy registered
[  473.827828] RPC: AUTH_GSS upcall timed out.
[  473.827828] Please check user daemon is running.


What is the problem, how can I fix it?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/