* loop device failure on 5.19-rc1 RISC-V
@ 2022-06-11 9:46 Ron Economos
2022-06-13 14:32 ` Christoph Hellwig
0 siblings, 1 reply; 3+ messages in thread
From: Ron Economos @ 2022-06-11 9:46 UTC (permalink / raw)
To: linux-block; +Cc: hch
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
solves the issue.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: loop device failure on 5.19-rc1 RISC-V
2022-06-11 9:46 loop device failure on 5.19-rc1 RISC-V Ron Economos
@ 2022-06-13 14:32 ` Christoph Hellwig
2022-06-13 14:50 ` Ron Economos
0 siblings, 1 reply; 3+ messages in thread
From: Christoph Hellwig @ 2022-06-13 14:32 UTC (permalink / raw)
To: Ron Economos; +Cc: linux-block, hch
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: loop device failure on 5.19-rc1 RISC-V
2022-06-13 14:32 ` Christoph Hellwig
@ 2022-06-13 14:50 ` Ron Economos
0 siblings, 0 replies; 3+ messages in thread
From: Ron Economos @ 2022-06-13 14:50 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: linux-block
On 6/13/22 07:32, Christoph Hellwig wrote:
> 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?
I'm using the kernel config file from Ubuntu 22.04 for RISC-V. It has
Amiga partitions enabled. I'll just disable it.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-06-13 18:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-06-11 9:46 loop device failure on 5.19-rc1 RISC-V Ron Economos
2022-06-13 14:32 ` Christoph Hellwig
2022-06-13 14:50 ` Ron Economos
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox