From: Marco Rebhan <me@dblsaiko.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Debugging NFS mounts
Date: Thu, 16 Nov 2023 21:38:45 +0100 [thread overview]
Message-ID: <1913374.2JyYDzQ6dc@invader> (raw)
In-Reply-To: <4526220.LvFx2qVVIh@wstn>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
On Wednesday, 15 November 2023 17:29:19 CET Peter Humphrey wrote:
> Hello list,
>
> My little server needs help with compiling, so I NFS-export /var (which has
> its own partition) to a chroot on my workstation. I mount all the partitions
> on both server and workstation. Then when I chroot, env-update hangs for
> ever. Well, over an hour anyway.
>
> Is it possible to export /var in this way? I can't see anything else wrong.
I don't see why it shouldn't work, but there's a couple commands I use to
debug NFS. They're not *great*, but they work.
I haven't used Gentoo in a while so I forget exactly what env-update does, but
I assume mounting the network share works successfully and this is just a
command that accesses /var.
You can use these commands to make the kernel driver output debugging
information to dmesg.
On the client:
> # rpcdebug -m nfs -s all
On the server:
> # rpcdebug -m nfsd -s all
On both sides, if the others don't give useful info, this is for the lower
level protocol:
> # rpcdebug -m rpc -s all
Then, try running the command again. It will spew a lot of info but hopefully
you can figure out from it what's going on.
-Marco :-)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-16 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 16:29 [gentoo-user] Debugging NFS mounts Peter Humphrey
2023-11-15 17:04 ` Alan McKinnon
2023-11-15 23:42 ` Peter Humphrey
2023-11-16 20:38 ` Marco Rebhan [this message]
2023-11-17 16:44 ` Peter Humphrey
2023-11-18 7:29 ` Peter Humphrey
2023-11-19 0:30 ` William Kenworthy
2023-11-19 15:12 ` Peter Humphrey
2023-11-19 15:59 ` [gentoo-user] " Remy Blank
2023-11-20 11:28 ` 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=1913374.2JyYDzQ6dc@invader \
--to=me@dblsaiko.net \
--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