From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] NFS tutorial for the brain dead sysadmin?
Date: Fri, 25 Jul 2014 19:47:15 -0700 [thread overview]
Message-ID: <lqv4ri$osk$1@ger.gmane.org> (raw)
In this case, the brain dead sysadmin would be moi :)
For years I've been using NFS to share /usr/portage with all of the
gentoo machines on my LAN.
Problem: occasionally it stops working for no apparent reason.
Example: two days ago I updated two ~amd64 gentoo machines, both of
which have been mounting /usr/portage as NFS3 shares for at least a
year with no problems.
One machine worked normally after the update, the other was unable to
mount /usr/portage because rpc.statd wouldn't start correctly.
After two frustrating days I discovered that I had never enabled the
rpcbind.service on the "broken" machine. So I enabled rpcbind, which
fixed the breakage.
So, why did the "broken" machine work normally for more than a year
without rpcbind until two days ago? (I suppose because nfs-utils was
updated to 1.3.0 ?)
The real problem here is that I have no idea how NFS works, and each
new version is more complicated because the devs are solving problems
that I don't understand or even know about.
So, please, what's the best way to learn and understand NFS?
Thanks for any clues.
next reply other threads:[~2014-07-26 2:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 2:47 walt [this message]
2014-07-26 13:51 ` [gentoo-user] NFS tutorial for the brain dead sysadmin? Alan McKinnon
2014-07-27 14:30 ` Tom H
2014-07-27 16:25 ` Stefan G. Weichinger
2014-07-27 16:55 ` J. Roeleveld
2014-07-27 19:44 ` Kerin Millar
2014-07-28 13:58 ` J. Roeleveld
2014-07-28 15:29 ` behrouz khosravi
2014-07-28 15:57 ` Neil Bothwick
2014-07-29 7:49 ` behrouz khosravi
2014-07-29 8:15 ` Peter Humphrey
2014-07-29 8:23 ` behrouz khosravi
2014-07-27 17:07 ` Stefan G. Weichinger
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='lqv4ri$osk$1@ger.gmane.org' \
--to=w41ter@gmail.com \
--cc=gentoo-user@lists.gentoo.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