linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sun, 11 Apr 2021 07:45:41 +0300	[thread overview]
Message-ID: <CAOQ4uxhw+a7NFpAiqVC9pZNSaWh+-RPsv2okym3UNOo=mGGC6Q@mail.gmail.com> (raw)
In-Reply-To: <6071FDE0.2070009@tlinx.org>

On Sat, Apr 10, 2021 at 10:34 PM L A Walsh <lkml@tlinx.org> wrote:
>
> On 2021/04/08 22:44, Amir Goldstein wrote:
> > 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.
> >
> ---
>     I can understand that, the upper layer is an empty fs+work dir

You must mean empty fs+upper dir+work dir. No?

> with no changes.  It was attached to the wrong lower layer,
> unattached/unmounted.
>
>     I then made sure both upper+work were both empty and tried again
> elsewhere.  I want to avoid unnecessary steps, so destroying and recreating
> an empty partition didn't seem logical.

I am probably missing something. How is this complicated?
rmdir upperdir workdir; mkdir upperdir workdir

> How do you disassociate a
> previous connected state?  What needs to be initialized on the
> unmounted upper and working dir (on the same fs), to reuse the same
> file system?
>

You need to remove the trusted.overlay.* xattrs, but I still don't
understand what's the complication with re-creating two empty dirs.

Thanks,
Amir.

      reply	other threads:[~2021-04-11  4:45 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
2021-04-10 19:34   ` L A Walsh
2021-04-11  4:45     ` Amir Goldstein [this message]

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='CAOQ4uxhw+a7NFpAiqVC9pZNSaWh+-RPsv2okym3UNOo=mGGC6Q@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).