linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Carl Karsten <carl@nextdayvideo.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: failed to verify upper - halts boot
Date: Tue, 7 Dec 2021 07:55:01 +0200	[thread overview]
Message-ID: <CAOQ4uxgb4cGHS9ZU-LfJAzSnmFDQmZgEBwHHA-J+G520gVsCyg@mail.gmail.com> (raw)
In-Reply-To: <CADmzSSjKoiYn7moEVFDV2p+x2BuTnWBLMBtdPQYsqQOttcgN1A@mail.gmail.com>

On Tue, Dec 7, 2021 at 4:38 AM Carl Karsten <carl@nextdayvideo.com> wrote:
>
> I powercyced my box, I'm assuming I did a sudo poweroff or halt or
> something, but maybe not.
>
> It got stuck, (enter rescue mode, root account disabled, hit enter to
> enter rescue mode... )  so I killed power.
>
> I edited fstab, changed auto to noauto, booted.
>
> overlay   /srv/nfs/rpi/bullseye/boot/merged    overlay
> noauto,defaults,ro,lowerdir=/srv/nfs/rpi/bullseye/boot/updates:/srv/nfs/rpi/bullseye/boot/setup:/srv/nfs/rpi/bullseye/boot/base,upperdir=/srv/nfs/rpi/bullseye/boot/play,workdir=/srv/nfs/rpi/bullseye/boot/work,nfs_export=on
>    0   0
>
> # mount /srv/nfs/rpi/bullseye/boot/merged
> mount: /srv/nfs/rpi/bullseye/boot/merged: mount(2) system call failed:
> Stale file handle.
>
> dmesg shows:
>
> [   45.941350] overlayfs: failed to verify upper (boot/play,
> ino=379405, err=-116)
> [   45.941369] overlayfs: failed to verify index dir 'upper' xattr
> [   45.941379] overlayfs: try deleting index dir or mounting with '-o
> index=off' to disable inodes index.
>

Did you by any change re-create boot/play dir without re-creating
boot/work dir? because that is what that message means.
I doubt it has to do with the power cycle.

> It is a bit concerning that I need to consider a power cycle may
> require local console use.  I plan on managing this remotely.  For now
> I'll leave it noauto and remotely mount when needed.  so this isn't a
> critical blocker to me.
>
> What would happen:  errors=remount-ro
>
> errors={continue|remount-ro|panic}
>     Define the behavior  when  an  error  is  encountered.  The
> default is set in the filesystem superblock,  ...     and can be
> changed using tune2fs(8).
>

This looks like a quote from the man page section about ext2 mount options.
Those are not options supported for overlayfs.

Anyway, with that error, as the kernel log says, you could have mounted
overlayfs ro with -o index=off and we could have added a mount option
to fallback to ro mount with index=off, but that means no nfs_export,
so not sure if that is what you wanted.

Thanks,
Amir.

  parent reply	other threads:[~2021-12-07  5:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05  1:04 failed to verify upper - halts boot Carl Karsten
2021-12-05  1:13 ` Carl Karsten
2021-12-07  5:55 ` Amir Goldstein [this message]
2021-12-07 21:17   ` Carl Karsten
2021-12-08  7:01     ` 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=CAOQ4uxgb4cGHS9ZU-LfJAzSnmFDQmZgEBwHHA-J+G520gVsCyg@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=carl@nextdayvideo.com \
    --cc=linux-unionfs@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 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).