linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carl Karsten <carl@nextdayvideo.com>
To: overlayfs <linux-unionfs@vger.kernel.org>
Subject: failed to verify upper - halts boot
Date: Sat, 4 Dec 2021 17:04:31 -0800	[thread overview]
Message-ID: <CADmzSSjKoiYn7moEVFDV2p+x2BuTnWBLMBtdPQYsqQOttcgN1A@mail.gmail.com> (raw)

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.

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).

In normal operation I want the mount ro anyway.
continue unmounted is also an option.  which would be better than
noauto if I am assured it won't get stuck at boot.

-- 
Carl K

             reply	other threads:[~2021-12-05  1:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05  1:04 Carl Karsten [this message]
2021-12-05  1:13 ` failed to verify upper - halts boot Carl Karsten
2021-12-07  5:55 ` Amir Goldstein
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=CADmzSSjKoiYn7moEVFDV2p+x2BuTnWBLMBtdPQYsqQOttcgN1A@mail.gmail.com \
    --to=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).