From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NFS mounting
Date: Mon, 21 Oct 2024 09:22:37 +0100 [thread overview]
Message-ID: <2345896.ElGaqSPkdT@rogueboard> (raw)
In-Reply-To: <2345314.ElGaqSPkdT@cube>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
On Monday 21 October 2024 03:12:23 BST Peter Humphrey wrote:
> On Friday 18 October 2024 15:55:19 BST Michael wrote:
>
> --->8
>
> > exportfs -rav
>
> Ah! I knew about 'exportfs -r' but not the 'av'. When I added that I got
> this:
>
> exportfs: duplicated export entries:
> exportfs:
> :192.168.178.7(rw,sync,insecure,no_subtree_check,all_squash,anonuid=250,ano
> ngid=250) exportfs:
> :192.168.178.7(rw,sync,insecure,no_subtree_check,all_squash,anonuid=250,ano
> ngid=250) exporting :/mnt/nfs/portage.packages
> exporting
> :192.168.178.7(rw,sync,insecure,no_subtree_check,all_squash,anonuid=250,ano
> ngid=250) exportfs: Failed to stat
> 192.168.178.7(rw,sync,insecure,no_subtree_check,all_squash,anonuid=250,anon
> gid=250): No such file or directory exporting :/mnt/nfs/portage
> exporting :192.168.178.7(rw,sync,no_subtree_check,crossmnt,fsid=0)
> exportfs: Failed to stat
> 192.168.178.7(rw,sync,no_subtree_check,crossmnt,fsid=0): No such file or
> directory
>
> Of course there's a duplicate export entry; I'm exporting two directories to
> the one machine. Well, three actually, counting the top-level one,
> /mnt/nfs. But is that duplication the cause of the 'Failed to stat...'?
>
> Do I need to set some opotions on an rpc service, or something?
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=250,anongid=250)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-10-21 8:23 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 [this message]
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
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=2345896.ElGaqSPkdT@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