From: Christoph Hellwig <hch@lst.de>
To: Ron Economos <w6rz@comcast.net>
Cc: linux-block@vger.kernel.org, hch@lst.de
Subject: Re: loop device failure on 5.19-rc1 RISC-V
Date: Mon, 13 Jun 2022 16:32:10 +0200 [thread overview]
Message-ID: <20220613143210.GB4110@lst.de> (raw)
In-Reply-To: <849cea40-4665-14fe-fa46-e555af730214@comcast.net>
On Sat, Jun 11, 2022 at 02:46:33AM -0700, Ron Economos wrote:
> The following error messages occur on 5.19-rc1 RISC-V Ubuntu 22.04:
>
> Jun 08 21:00:20 riscv64 kernel: Dev loop0: unable to read RDB block 8
> Jun 08 21:00:20 riscv64 kernel: loop0: unable to read partition table
> Jun 08 21:00:20 riscv64 kernel: loop0: partition table beyond EOD, truncated
>
> This happens when the snapd daemon tries to mount loop0.
>
> Reverting commit b9684a71fca793213378dd410cd11675d973eaa1
>
> block, loop: support partitions without scanning
In which case the snapd daemon explicitly asks for a partitions scan,
and we fixed a regression that makes it behave like it did in 5.16
and earlier. But why do you have support for Amiga partitions enabled
on RISC-V anyway?
next prev parent reply other threads:[~2022-06-13 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 9:46 loop device failure on 5.19-rc1 RISC-V Ron Economos
2022-06-13 14:32 ` Christoph Hellwig [this message]
2022-06-13 14:50 ` Ron Economos
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=20220613143210.GB4110@lst.de \
--to=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=w6rz@comcast.net \
/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