From: Amir Goldstein <amir73il@gmail.com>
To: "L. A. Walsh" <lkml@tlinx.org>
Cc: overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: odd error: why: mount: /home2: mount(2) system call failed: Stale file handle
Date: Fri, 9 Apr 2021 08:44:28 +0300 [thread overview]
Message-ID: <CAOQ4uxj4bdzcdcy7jpkRCZTNv=4b8BPVVP+1L_3OLWFwMnV-kQ@mail.gmail.com> (raw)
In-Reply-To: <606F526A.1040405@tlinx.org>
On Thu, Apr 8, 2021 at 10:18 PM L. A. Walsh <lkml@tlinx.org> wrote:
>
> Started to try overlay fs w/one fs, but decided on another, so
> umounted the first -- hadn't done any changes.
>
> Then tried a different lower dir (/home) and tried to mount into new
> dir /home2. Got:
> mount: /home2: mount(2) system call failed: Stale file handle
>
> any idea why? I cleared out contents of workdir (two empty dirs)
> but still didn't work again.
>
> running a Vanilla-ish self-made kernel version 5.9.2...
> don't know what other info I should provide...oh well...
>
You should normally at least look at kmsg, where you are likely to
find "overlayfs: failed to verify upper root origin".
It is generally not allowed to reuse the upper layer and replace the
lower layers after overlayfs has been mounted once.
If you say you did not change anything, it is not clear what is the
benefit of reusing the empty upper layer.
Thanks,
Amir.
next prev parent reply other threads:[~2021-04-09 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 18:58 odd error: why: mount: /home2: mount(2) system call failed: Stale file handle L. A. Walsh
2021-04-09 5:44 ` Amir Goldstein [this message]
2021-04-10 19:34 ` L A Walsh
2021-04-11 4:45 ` Amir Goldstein
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='CAOQ4uxj4bdzcdcy7jpkRCZTNv=4b8BPVVP+1L_3OLWFwMnV-kQ@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=lkml@tlinx.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;
as well as URLs for NNTP newsgroup(s).