public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NFS tutorial for the brain dead sysadmin?
Date: Sun, 27 Jul 2014 18:55:24 +0200	[thread overview]
Message-ID: <065b33b7-e8ad-48d4-8e83-7743b8da7d02@email.android.com> (raw)
In-Reply-To: <53D527F4.5080108@xunil.at>

On 27 July 2014 18:25:24 CEST, "Stefan G. Weichinger" <lists@xunil.at> wrote:
>Am 26.07.2014 04:47, schrieb walt:
>
>> 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.
>
>I double your search for understanding ... my various efforts to set up
>NFSv4 for sharing stuff in my LAN also lead to unstable behavior and
>frustration.
>
>Only last week I re-attacked this topic as I start using puppet here to
>manage my systems ... and one part of this might be sharing
>/usr/portage
>via NFSv4. One client host mounts it without a problem, the thinkpads
>don't do so ... just another example ;-)
>
>Additional in my context: using systemd ... so there are other
>(different?) dependencies at work and services started.
>
>I'd be happy to get that working in a reliable way. I don't remember
>unstable behavior with NFS (v2 back then?) when we used it at a company
>I worked for in the 90s.
>
>Stefan

I use NFS for filesharing between all wired systems at home.
Samba is only used for MS Windows and laptops.

Few things I always make sure are valid:
- One partition per NFS share
- No NFS share is mounted below another one
- I set the version to 3 on the clients
- I use LDAP for the user accounts to ensure the UIDs and GIDs are consistent.

NFS4 requires all the exports to be under a single foldertree.

I haven't had any issues in the past 7+ years with this and in the past 5+ years I had portage, distfiles and packages shared.
/etc/portage is symlinked to a NFS share as well, allowing me to create binary packages on a single host (inside a chroot) which are then used to update the different machines.

If anyone wants a more detailed description of my setup. Let me know and I will try to write something up.

Kind regards

Joost

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


  reply	other threads:[~2014-07-27 16:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26  2:47 [gentoo-user] NFS tutorial for the brain dead sysadmin? walt
2014-07-26 13:51 ` Alan McKinnon
2014-07-27 14:30   ` Tom H
2014-07-27 16:25 ` Stefan G. Weichinger
2014-07-27 16:55   ` J. Roeleveld [this message]
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=065b33b7-e8ad-48d4-8e83-7743b8da7d02@email.android.com \
    --to=joost@antarean.org \
    --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