From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] nfs mounting
Date: Thu, 31 Oct 2024 09:52:23 +0000 [thread overview]
Message-ID: <1952017.taCxCBeP46@rogueboard> (raw)
In-Reply-To: <4943483.GXAFRqVoOG@cube>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On Wednesday 30 October 2024 23:24:19 GMT Peter Humphrey wrote:
> On Thursday 17 October 2024 16:00:36 GMT I wrote:
>
> --->8
>
> Well, it looks as though I have it working, over an Ethernet link anyway.
> There's now no /mnt/nfs with fsid=0, with the portage tree and the packages
> directory mounted below it. This is /etc/exports on the i5:
>
> /var/db/repos/gentoo
> wstn.prhnet(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250
> ,anongid=250)
> /var/cache/packages
> wstn.prhnet(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250
> ,anongid=250)
>
> Those are just two long lines. Breaking them seemed to cause problems. You
> see that there's no intermediate mount point.
Yes, the /etc/exports syntax is sensitive to breaks or spaces. There should
be a single space between the exported directory and the client's hostname or
IP address and no more.
> The last two weeks' work has left me unsure of the integrity of the i5, so
> I'm going to install a fresh new system and save it before tackling the
> wireless link. Then I may be able to coil up that great long Ethernet cable
> and stow it.
Hmm ... if your NFS configuration works over wired ethernet, but not over
wireless, this could point to a lower network level problem.
I tend to use static IP addresses on both endpoints to simplify checks and
configuration, but if you use hostnames check reverse name resolution is
correct and adjust your /etc/hosts on both ends, check the DNS configuration
on your LAN and check the client/server IP allocations are as they should be.
Temporarily disable firewalls on both ends and check connectivity and access
to NFS ports 111,2049 on the server.
Check firewall logs/rules on the wireless router and configure accordingly if
they are blocking.
Finally, make sure hostnames/IP addresses are correctly reflected on NFS
configuration at both ends.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-10-31 9:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 15:00 [gentoo-user] nfs mounting Peter Humphrey
2024-10-30 23:24 ` Peter Humphrey
2024-10-31 9:52 ` Michael [this message]
2024-10-31 11:07 ` Peter Humphrey
2024-10-31 14:21 ` Michael
2024-10-31 15:09 ` Peter Humphrey
-- strict thread matches above, loose matches on Subject: below --
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
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
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=1952017.taCxCBeP46@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