From: Christoph Hellwig <hch@lst.de>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org
Subject: Re: unable to read RDB block due to b9684a71fca793
Date: Wed, 6 Jul 2022 10:09:12 +0200 [thread overview]
Message-ID: <20220706080912.GA32273@lst.de> (raw)
In-Reply-To: <YsT5MGPNha1Z1i7V@debian.me>
On Wed, Jul 06, 2022 at 09:53:36AM +0700, Bagas Sanjaya wrote:
> Hi,
>
> I first noticed this issue on v5.18.9, and still found on v5.19-rc5.
>
> Looking at dmesg, I see error message on loop8 device:
>
> [ 41.319699] Dev loop8: unable to read RDB block 8
> [ 41.320566] loop8: unable to read partition table
> [ 41.320597] loop8: partition table beyond EOD, truncated
>
> My Debian 11 laptop is also run LXD (as development server).
>
> Bisecting between v5.18 and v5.19-rc5, the culprit is commit b9684a71fca793
> ("block, loop: support partitions without scanning").
Which just restores the previous behavior of optionally allowing to
scan for partitions on all loop devices. So that error had been
there before and just disappeared due to a regression.
next prev parent reply other threads:[~2022-07-06 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 2:53 unable to read RDB block due to b9684a71fca793 Bagas Sanjaya
2022-07-06 8:09 ` Christoph Hellwig [this message]
2022-07-06 10:16 ` Bagas Sanjaya
2022-07-06 12:00 ` Christoph Hellwig
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=20220706080912.GA32273@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bagasdotme@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
/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