From: Nix <nix@esperi.org.uk>
To: bfields@fieldses.org (J. Bruce Fields)
Cc: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: what on earth is going on here? paths above mountpoints turn into "(unreachable)"
Date: Wed, 04 Feb 2015 23:28:17 +0000 [thread overview]
Message-ID: <87r3u58df2.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <87egq6lqdj.fsf@spindle.srvr.nix> (nix@esperi.org.uk's message of "Tue, 03 Feb 2015 19:57:44 +0000")
On 3 Feb 2015, nix@esperi.org.uk outgrape:
> On 3 Feb 2015, J. Bruce Fields spake thusly:
>
>> On Tue, Feb 03, 2015 at 12:25:18AM +0000, Nix wrote:
>>> I'm seeing this bizarre output after a long delay (memory pressure not
>>> required: vapoursynth, which was running here, is using a couple of gig
>>> out of 16GiB, and the machine has 12GiB in buffers/cache):
>>>
>>> FileNotFoundError: [Errno 2] No such file or directory: '(unreachable)/Orphan-Black/1'
>>
>> Haven't really read this carefully, just noticed the ENOENT. There was
>> 49a068f82a "rpc: fix xdr_truncate_encode to handle buffer ending on page
>> boundary" recently, fixing a problem introduced in 3.16 that could I
>> think cause an enoent if Orphan-Black/ was a large-ish directory.
>
> It's got three files in it. Orphan-Black/1 has fifteen. Way under, say,
> a page.
>
> The problem hasn't recurred since I mounted /usr/archive and
> /usr/archive/series explicitly rather than relying on nohide, so I'd
> guess the problem lies there: it is, after all, evil.
It doesn't. It still recurs.
If I cd out of the tree entirely (say, to /tmp) then back in, the
mountpoint often reconnects for all its users: if I do things in there
(e.g. an ls) it always seems to. If I cd within the disconnected subtree
via a relative path, it doesn't.
So running this often helps:
while sleep 300; do cd /usr/archive/series/Orphan-Black/2; ls > /dev/null; cd /tmp; done
but not always -- if the thing vanishes <300s before the last problem,
we're still in for it.
--
NULL && (void)
next prev parent reply other threads:[~2015-02-04 23:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 0:25 what on earth is going on here? paths above mountpoints turn into "(unreachable)" Nix
2015-02-03 19:53 ` J. Bruce Fields
2015-02-03 19:57 ` Nix
2015-02-04 23:28 ` Nix [this message]
2015-02-05 0:26 ` NeilBrown
2015-02-10 17:48 ` Nix
2015-02-10 18:32 ` J. Bruce Fields
2015-02-11 23:07 ` Nix
2015-02-11 23:18 ` NeilBrown
2015-02-12 1:50 ` Nix
2015-02-12 15:38 ` J. Bruce Fields
2015-02-14 13:17 ` Nix
2015-02-16 2:46 ` NeilBrown
2015-02-16 3:57 ` NeilBrown
2015-02-17 17:32 ` Nix
2015-02-20 17:26 ` Nix
2015-02-20 21:03 ` NeilBrown
2015-02-16 4:28 ` Trond Myklebust
2015-02-16 4:54 ` NeilBrown
2015-02-22 22:13 ` Trond Myklebust
2015-02-22 22:47 ` NeilBrown
2015-02-23 2:05 ` Trond Myklebust
2015-02-23 2:33 ` Trond Myklebust
2015-02-23 3:05 ` NeilBrown
2015-02-23 3:33 ` Trond Myklebust
2015-02-23 4:49 ` NeilBrown
2015-02-23 13:55 ` Trond Myklebust
2015-02-16 15:43 ` J. Bruce Fields
2015-02-11 3:07 ` NeilBrown
2015-02-11 23:11 ` Nix
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=87r3u58df2.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.