public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NFS mounting
Date: Tue, 22 Oct 2024 14:36:17 +0100	[thread overview]
Message-ID: <13624495.uLZWGnKmhe@rogueboard> (raw)
In-Reply-To: <2760373.mvXUDI8C0e@cube>

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

On Tuesday 22 October 2024 13:00:14 BST Peter Humphrey wrote:
> On Tuesday 22 October 2024 10:14:48 BST Michael wrote:
> > On Tuesday 22 October 2024 02:10:45 BST Peter Humphrey wrote:
> > > On Monday 21 October 2024 09:22:37 BST Michael wrote:
> > > > Assuming all required directories are on the same fs, what happens if
> > > > you
> > > > *only* export the parent directory?  Something like this:
> > > > 
> > > > /mnt/nfs \
> > > > 192.168.178.7/32(rw,sync,insecure,no_subtree_check,all_squash,anonuid=
> > > > 25
> > > > 0,
> > > > an ongid=250)
> > > 
> > > Actually, the converse turned out to be right. Removing the top-level
> > > /mnt/nfs spec from /etc/exports allowed the whole thing to spring into
> > > life.
> > > 
> > > Go figure, as they say in the colonies.  ;)
> > 
> > I'm glad you 'figured' this, although puzzled by your solution.  In my
> > experience I only needed to export one directory only as the top
> > directory,
> > for each different partition.
> 
> I followed the Gentoo NFS wiki page, which says "this article demonstrates a
> best-practice NFSv4 deployment using a virtual root".

If you are referring to the NFS-utils wiki page:

https://wiki.gentoo.org/wiki/Nfs-utils

it provides an example of exporting two *different* partitions:

Device       Mount directory     Description
/dev/sdb1	   /home               Filesystem containing user home directories.
/dev/sdc1	   /data               Filesystem containing user data.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-10-22 13:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 13:41 [gentoo-user] NFS mounting Peter Humphrey
2024-10-18 14:55 ` Michael
2024-10-21  2:12   ` Peter Humphrey
2024-10-21  5:47     ` William Kenworthy
2024-10-21  8:22     ` Michael
2024-10-22  1:10       ` Peter Humphrey
2024-10-22  9:14         ` Michael
2024-10-22 12:00           ` Peter Humphrey
2024-10-22 13:36             ` Michael [this message]
2024-10-22 17:01               ` Matt Jolly
2024-10-22 19:29                 ` Michael
2024-10-22 21:07                   ` Peter Humphrey
2024-10-23 10:56                     ` Peter Humphrey
2024-10-23 11:36                       ` Arve Barsnes
2024-10-23 12:17                         ` Peter Humphrey
2024-10-18 15:40 ` Jack Ostroff
2024-10-18 16:50 ` [gentoo-user] " Grant Edwards
  -- strict thread matches above, loose matches on Subject: below --
2024-10-17 15:00 [gentoo-user] nfs mounting Peter Humphrey
2024-10-30 23:24 ` Peter Humphrey
2024-10-31  9:52   ` Michael
2024-10-31 11:07     ` Peter Humphrey
2024-10-31 14:21       ` Michael
2024-10-31 15:09         ` Peter Humphrey

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=13624495.uLZWGnKmhe@rogueboard \
    --to=confabulate@kintzios.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