From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] nfs mounting
Date: Thu, 17 Oct 2024 16:00:36 +0100 [thread overview]
Message-ID: <10555432.nUPlyArG6x@cube> (raw)
Greetings,
It's me again with another tyro problem.
I'm trying to set up my big Ryzen M9 workstation as compute host for my
desktop PC, which is an i5 NUCI. I had the same arrangement working well with
the i5's predecessor, but I can't make it work this time.
The idea is to NFS-export the i5's portage and packages directories to the M9,
which mounts it in a chroot partition to work on it. The M9 is on the wored
LAN, the i5 uses WiFi to connect through the ADSL modem-router. The M9 has a
separate partition for the chroot, but the i5 portage tree and packages
directory both live under the /var partition.
I've used the same script and file-system layout on the M9 as before, merely
adjusting the IP address.
# mount /mnt/nuci
# mount -t nfs 192.168.178.40:/mnt/nfs/portage /mnt/nuci/var/db/repos/gentoo
mount.nfs: mounting 192.168.178.40:/mnt/nfs/portage failed, reason given by
server: No such file or directory
That reply comes about 15s after the mount command, so DNS is working and
traffic is flowing between the machines.
This is /etc/exports on the i5:
/mnt/nfs \
192.168.178.7(rw,sync,no_subtree_check,anonuid=250,anongid=250,crossmnt,fsid=0)
/mnt/nfs/portage \
192.168.178.7(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250)
/mnt/nfs/portage.packages \
192.168.178.7(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250)
$ ls -la /mnt/nfs/portage | head
total 1.1M
drwxr-xr-x 179 root portage 4.0K Sep 20 10:27 .
drwxr-xr-x 4 root root 4.0K Oct 8 14:21 ..
drwxr-xr-x 451 portage portage 12K Sep 5 15:51 acct-group
drwxr-xr-x 421 portage portage 12K Sep 5 15:51 acct-user
drwxr-xr-x 27 portage portage 4.0K Sep 3 14:36 app-accessibility
drwxr-xr-x 194 portage portage 4.0K Oct 1 12:13 app-admin
drwxr-xr-x 12 portage portage 4.0K Sep 3 14:36 app-alternatives
drwxr-xr-x 6 portage portage 4.0K Sep 3 14:36 app-antivirus
drwxr-xr-x 111 portage portage 4.0K Sep 3 14:36 app-arch
Everything under /mnt/nfs/portage has owner portage:portage. (I found that
necessary on the earlier setup, so it's the same here.)
I've checked the firewall settings and logs; no problems found. Both kernels
have NFSv3 and v4, but not 4.1 or 4.2. What else can I check?
--
Regards,
Peter.
next reply other threads:[~2024-10-17 15:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 15:00 Peter Humphrey [this message]
2024-10-30 23:24 ` [gentoo-user] nfs mounting 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
-- 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=10555432.nUPlyArG6x@cube \
--to=peter@prh.myzen.co.uk \
--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