linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael D Labriola <michael.d.labriola@gmail.com>
To: linux-unionfs@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
	Michael D Labriola <michael.d.labriola@gmail.com>
Subject: Re: failed open: No data available
Date: Tue, 15 Dec 2020 10:32:11 -0500	[thread overview]
Message-ID: <2n1rfrf5l0.fsf@aldarion.sourceruckus.org> (raw)
In-Reply-To: <2nv9d47zt7.fsf@aldarion.sourceruckus.org>

On Mon, Dec 14, 2020 at 6:06 PM Michael D Labriola <michael.d.labriola@gmail.com> wrote:
>
> I'm sporatically getting "no data available" as a reason to fail to
> open files on an overlay mount.  Most obvious is during ln of backup
> file during apt install.  Only seems to happen on copy_up from lower
> layer.  Lower layer is squashfs (I've seen it happen with both the
> default zlib and also zstd compression), upper is EXT4.
>
> I've only bumped into this problem recently with 5.9+ kernels.  I'm
> gonna go see if I can reproduce in some older kernels I still have
> installed.

Rebooting into 5.4 made the problem go away and I can apt upgrade
w/out any problems.  Rebooting an affected virtual machine into 5.8
also fixed the problem, so it looks to be something introduced in 5.9.

I suppose I should try 5.10 and see if this problem has already been
fixed.

>
> Anyone else reporting this?


-- 
Michael D Labriola
21 Rip Van Winkle Cir
Warwick, RI 02886
401-316-9844 (cell)

  reply	other threads:[~2020-12-15 15:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 23:06 failed open: No data available Michael D Labriola
2020-12-15 15:32 ` Michael D Labriola [this message]
2020-12-15 16:31   ` Amir Goldstein
2020-12-15 19:29     ` Michael Labriola
2020-12-16  6:04       ` Amir Goldstein
2020-12-16 19:49         ` Michael Labriola
2020-12-16 23:01           ` Michael Labriola
2020-12-17 12:00             ` Amir Goldstein
2020-12-17 16:22               ` Michael Labriola
2020-12-17 18:06                 ` Amir Goldstein
2020-12-17 19:46                   ` Michael Labriola
2020-12-17 20:25                     ` Amir Goldstein
2020-12-17 21:56                       ` Michael Labriola
2020-12-17 23:47                         ` Michael Labriola
2020-12-18  7:02                           ` Amir Goldstein
2020-12-18 20:47                             ` Michael Labriola
2020-12-18 22:55                               ` Paul Moore
2020-12-19  9:52                               ` 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=2n1rfrf5l0.fsf@aldarion.sourceruckus.org \
    --to=michael.d.labriola@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).