[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-215712-13602-2iktX1lkDv@https.bugzilla.kernel.org/>
Date: Wed, 23 Mar 2022 23:06:36 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 215712] kernel deadlocks while mounting the image
https://bugzilla.kernel.org/show_bug.cgi?id=215712
Christian Kujau (lists@...dbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lists@...dbynature.de
--- Comment #3 from Christian Kujau (lists@...dbynature.de) ---
A 5.17 kernel *is* able to mount the image here, but it takes quite some time
to complete:
=======================================
$ time mount -v -t ext4 -o loop,ro,debug tmp.img /mnt/disk/
mount: /dev/loop0 mounted on /mnt/disk.
real 1m32.694s
user 0m0.008s
sys 1m32.665s
=======================================
During that time the CPU is spinning like crazy, but I don't know how to debug
this further as to why it's spinning. perf comes to mind, but maybe something
more ext4 specific is more useful here. dmesg shows, for this mount operation:
=======================================
[ 188.269405] [EXT4 FS bs=1024, gc=2, bpg=8192, ipg=2048, mo=a802c818,
mo2=0002]
[ 280.932637] EXT4-fs (loop0): mounted filesystem with ordered data mode.
Quota mode: disabled.
[ 595.249319] EXT4-fs (loop0): error count since last fsck: 1
[ 595.250559] EXT4-fs (loop0): initial error at time 1647888893:
ext4_mb_generate_buddy:756
[ 595.253403] EXT4-fs (loop0): last error at time 1647888893:
ext4_mb_generate_buddy:756
=======================================
@Ming, can you share details on how the image has been modified?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
Powered by blists - more mailing lists