From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ben DJ <bendj095124367913213465@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFSv4 Kernel-server requires 2x manual restart after reboot? Maybe a timing problem?
Date: Fri, 23 Oct 2009 13:27:19 -0400 [thread overview]
Message-ID: <20091023172719.GB31133@fieldses.org> (raw)
In-Reply-To: <babafd2f0910231007h329e75b7raa7207d0b816a72a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Oct 23, 2009 at 10:07:23AM -0700, Ben DJ wrote:
> I've installed NFSv4 as nfs-kernel-server.
What distro and versions are you using?
> I'm slowly figuring out
> how to get it to configured and working.
>
> After a system reboot, if I try to mount an export,
>
> mount -t nfs4 192.168.1.2:/test /mnt/test
>
> it just "sits there", never mounting.
>
> So I 1st check what's running,
>
> ps ax | egrep -i "idmapd|mountd|statd|nfsd|sm-notify"
> 3731 ? Ss 0:00 /usr/sbin/rpc.idmapd
> 3732 ? Ss 0:00 /usr/sbin/rpc.idmapd
> 3753 ? Ss 0:00 /usr/sbin/rpc.statd --no-notify
> 3758 ? S< 0:00 [nfsd4]
> 3759 ? S< 0:00 [nfsd]
> 3760 ? S< 0:00 [nfsd]
> 3761 ? S< 0:00 [nfsd]
> 3762 ? S< 0:00 [nfsd]
> 3772 ? Ss 0:00 /usr/sbin/rpc.mountd
>
> and that looks OK.
>
> After some experiments, I've discovered if I CTRL-C the mount attempt
> and restart the server TWICE,
>
> service nfsserver restart
> Shutting down kernel based NFS server: nfsd statd mountd
> done
> Starting kernel based NFS server: idmapdexportfs: Warning: /nfs/test
> does not support NFS export.
Huh. What filesystem is at /nfs/test?
--b.
> mountd statd nfsd sm-notify
> done
>
> service nfsserver restart
> Shutting down kernel based NFS server: nfsd statd mountd
> done
> Starting kernel based NFS server: idmapd mountd statd nfsd sm-notify
> done
>
> Notice that the 2nd time the "idmapd" appears to be re-started.
>
> then repeat the mount attempt,
>
> mount -t nfs4 192.168.1.2:/test /mnt/test
>
> it now works.
>
> Checking what's running again,
>
> ps ax | egrep -i "idmapd|mountd|statd|nfsd|sm-notify"
>
> 3731 ? Ss 0:00 /usr/sbin/rpc.idmapd
> 3732 ? Ss 0:00 /usr/sbin/rpc.idmapd
> 5213 ? S<s 0:00 /usr/sbin/rpc.mountd
> 5216 ? S<s 0:00 /usr/sbin/rpc.statd --no-notify
> 5221 ? S< 0:00 [nfsd4]
> 5222 ? S< 0:00 [nfsd]
> 5223 ? S< 0:00 [nfsd]
> 5224 ? S< 0:00 [nfsd]
> 5225 ? S< 0:00 [nfsd]
>
> It all looks the same as before. Notice that the rpc.idmapd PIDs are
> the same, even though the "service nfsserver restart" 2nd time around
> looked like it restarted it.
>
> I don't really understand what the 2X nfsserver restart does. There
> clearly IS an effect. And it looks like it has to do with idmapd.
>
> I can say that
>
> service nfsserver stop
> service nfs stop
> service quotad stop
> service rpcbind stop
> umount -a
> mount -a
> service rpcbind start
> service quotad start
> service nfs start
> service nfsserver start
>
> often gives me similar errors,
>
> Warning: /nfs/test does not support NFS export
>
> that go away if I make sure there's a delay after starting nfs,
>
> service nfs start && sleep 5
> service nfsserver start
>
> Maybe there's some sort of timing problem on startup?
>
> Any clues?
>
> BenDJ
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-23 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 17:07 NFSv4 Kernel-server requires 2x manual restart after reboot? Maybe a timing problem? Ben DJ
[not found] ` <babafd2f0910231007h329e75b7raa7207d0b816a72a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-23 17:27 ` J. Bruce Fields [this message]
2009-10-23 17:57 ` Ben DJ
[not found] ` <babafd2f0910231057o4898c643n4605ef9b0e4686d8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-23 18:24 ` J. Bruce Fields
2009-10-23 19:12 ` Ben DJ
2009-10-27 4:34 ` Suresh Jayaraman
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=20091023172719.GB31133@fieldses.org \
--to=bfields@fieldses.org \
--cc=bendj095124367913213465@gmail.com \
--cc=linux-nfs@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