From: DimanNe <dimanne@ya.ru>
To: linux-kernel@vger.kernel.org
Subject: nfs mount fails on startup
Date: Wed, 18 Sep 2013 12:04:49 +0400 [thread overview]
Message-ID: <342091379491489@web28m.yandex.ru> (raw)
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@Impedance:~$ 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@Impedance:~$ 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?
reply other threads:[~2013-09-18 8:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=342091379491489@web28m.yandex.ru \
--to=dimanne@ya.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®