From: Nix <nix@esperi.org.uk>
To: "bfields\@fieldses.org" <bfields@fieldses.org>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
"linux-nfs\@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: steam-associated reproducible hard NFSv4.2 client hang (5.9, 5.10)
Date: Thu, 01 Apr 2021 22:52:47 +0100 [thread overview]
Message-ID: <87eeftlljk.fsf@esperi.org.uk> (raw)
In-Reply-To: <20210401134442.GB13277@fieldses.org> (bfields@fieldses.org's message of "Thu, 1 Apr 2021 09:44:42 -0400")
On 1 Apr 2021, bfields@fieldses.org outgrape:
> On Thu, Apr 01, 2021 at 02:33:02PM +0100, Nix wrote:
>> [Sorry about the huge delay: your replies got accidentally marked as
>> read in a MUA snafu. I'll be getting some more debugging dumps -- and
>> seeing if this still happens! -- when I reboot into 5.11 this weekend.]
>>
>> On 24 Feb 2021, bfields@fieldses.org said:
>>
>> > On Tue, Feb 23, 2021 at 11:58:51PM +0000, Trond Myklebust wrote:
>> >> On Tue, 2021-02-23 at 17:57 -0500, J. Bruce Fields wrote:
>> >> > On Sun, Jan 03, 2021 at 02:27:51PM +0000, Nick Alcock wrote:
>> >> > > Relevant exports, from /proc/fs/nfs/exports:
>> >> > >
>> >> > > / 192.168.16.0/24,silk.wkstn.nix(ro,insecure,no_root_squash,s
>> >> > > ync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=0a4a4563:00764033
>> >> > > :8c827c0e:989cf534,sec=390003:390004:390005:1)
>> >> > > /home/.loom.srvr.nix *.srvr.nix,fold.srvr.nix(rw,root_squash,syn
>> >> > > c,wdelay,no_subtree_check,uuid=0a4a4563:00764033:8c827c0e:989cf534,
>> >> > > sec=1)
>> >>
>> >> Isn't that trying to export the same filesystem as '/' on the line
>> >> above using conflicting export options?
>>
>> Hmm. I don't actually have a / mount in /etc/exports (and haven't had
>> one since I finished building this machine, last year), and looking at
>> /proc/fs/nfs/exports on the server now, it's not there.
>
> Right, but even though you're not exporting /, you're exporting
> /home/.loom.srvr.nix, and that's on the same filesystem as /, isn't it?
Yes, but I'm *not* exporting /. (I just checked my backups, and no such
export existed at the time I sent the original mail, nor was I importing
it on the client).
This export is prsumably automatically generated, and likely indicates
nothing more than that I am exporting from different subtrees off the
root (which I am: various subdirectories of /home, /usr, /trees,
/.transient, /.nfs, and /pkg are exported).
next prev parent reply other threads:[~2021-04-01 21:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 14:27 steam-associated reproducible hard NFSv4.2 client hang (5.9, 5.10) Nick Alcock
2021-02-23 22:57 ` J. Bruce Fields
2021-02-23 23:58 ` Trond Myklebust
2021-02-24 2:01 ` bfields
2021-04-01 13:33 ` Nix
2021-04-01 13:44 ` bfields
2021-04-01 21:52 ` Nix [this message]
2021-04-02 19:20 ` bfields
2021-04-03 22:41 ` Nix
2021-04-05 11:48 ` Nix
2021-04-05 16:52 ` Nix
-- strict thread matches above, loose matches on Subject: below --
2021-02-13 15:21 Nick Alcock
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=87eeftlljk.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.com \
/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