On 2014-08-14 12:36 (GMT-0700) Andrew Lutomirski composed:
J. Bruce Fields wrote:
> On Tue, Aug 12, 2014 at 12:58:13AM -0400, Felix Miata wrote:
>> Why when nothing is automounting nfs either as client or
server does boot
>> not proceed to completion without a 2+ minute pause while nfs-server fails
>> to start?
> Sounds like a bug. Is the failure to start expected?
Not expected by me.
I wonder whether https://bugzilla.redhat.com/show_bug.cgi?id=1129425
related. It's possible for nfs client mounts to start a copy of rpc.statd
that systemd doesn't know about.
I can't tell whether that's related or not. The only significant NFS problem
I can remember before this, once I originally figured out what little I
needed to figure out about NFS eons ago when setting up a LAN for the first
time, had to do with rpcbind replacing portmap.
> > Exportfs never (on my installations) needed fsid= in
> > before, why the complaint about its absence now, and with output of
> > showmount -e showing no signs of having failed?
> fsid=0 shouldn't be required. Probably file a bug with the
The problem with that is I can't tell what the difference is between the
systems with the problem and those without. Also I haven't tried to keep up
with which do or don't. I have roughly 10 each with F21 and with Rawhide.
Lately it seems as though the problem may be disappearing on its own as the
updates keep coming in.
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/