Forgot to mention you also need coreutils-9.0 or later, or some other
program that uses lseek SEEK_HOLE/SEEK_DATA as that is the culprit for
the bug. Essentially it errorneously reports holes in files that are
still dirty buffers. I had a local copy of "cp" from coreutils/sid
compiled for jammy.
Reproducible on Ubuntu 22.04 LTS w/ linux-hwe-6.2 (zfs-2.1.9) using the
NixOS test suite:
[zhammer::647] checking 1 files at iteration 0
[zhammer::647] zhammer_647_0 differed from zhammer_647_576!
[zhammer::647] Hexdump diff follows
--- zhammer_647_0.hex 2023-11-30 15:37:43.887596987 +
+
It appears upstream is prepping a 2.1.14 and 2.2.2 release that includes this
fix to both branches.
https://github.com/openzfs/zfs/pull/15601
https://github.com/openzfs/zfs/pull/15602
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
Apparently 2.2.1 did not fix the issue, there is an on-going PR
https://github.com/openzfs/zfs/pull/15571 that has the latest fix for
the data corruption. As a side note it also affects zfs 2.1 series
(block cloning made it more evident, but apparently possible to happen
on earlier zfs releases),
Comment #5 (https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-5.11/+bug/1942935/comments/5) has been a stable workaround for me
(basically revert back to a continuous resync like 18.04).
My newer machines are using ZFS with raidz2 pools.
--
You received this bug notification because yo
Yeah, that's the same issue as this one. The issue is the raid is doing
a consistency check (mdcheck) and is transitioned to an "idle" state and
hits a deadlock that causes all I/O through the md device to block. The
workaround is to change the array state back to active.
I made the changes in #
I believe to resolve the deadlock you want to do:
echo active > /sys/block/md1/md/array_state
Not "idle". You should see a hung task for mdcheck in there somewhere as well,
and it only occurs when the raid is resyncing (md_resync should be running), at
least for me I the workaround in comment 5:
Looks like two patches are landing in next to resolve this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220527&id=8b48ec23cc51a4e7c8dbaef5f34ebe67e1a80934
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20220527&id=1e267742
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526040/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launc
Same issue on impish 5.13.13 kernel, running in VBox.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1942935
Title:
kernel io hangs during mdcheck/resync
Status in linux
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526038/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526036/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526037/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526039/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526034/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526035/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu
apport information
** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526031/+files/Card0.Codecs.codec97.0.ac97.0-0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
apport information
** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.regs.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526032/+files/Card0.Codecs.codec97.0.ac97.0-0.regs.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526033/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bu
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526030/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/1942935/+attachment/5526029/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs
** Patch added: "md-reap-sync-thread.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942935/+attachment/5526028/+files/md-reap-sync-thread.patch
** Tags added: apport-collected impish
** Description changed:
It seems to always occur during an mdcheck/resync, if I am logged in
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1942935
Title:
kernel io hangs during mdcheck/resync
** Tags removed: hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1942935
Title:
kernel io hangs during mdcheck/resync
Status in linux package in Ubuntu:
Incompl
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1942935
Title:
kernel io hangs during mdcheck/r
Here is Donald Buczek's reproducer script. I setup an Ubuntu 20.04 VM
with latest linux-image-generic and was able to reproduce it within
maybe 10 or 15 minutes. Exactly the same issue.
Filesystem layout built as follows:
# assemble raid devices
mdadm --create /dev/md0 --level=1 --raid-devices=
The patch hasn't made it into mainline from what I have seen, it looks
like it died back in March waiting for feedback from additional kernel
developers. From what I have gathered this is a deadlock scenario
directly caused by pausing the resync while the system is under heavy
write activity.
Don
Here is the proposed patch, Doesn't appear to have been applied. Last
report was with 5.11rc5.
https://lore.kernel.org/linux-raid/1613177399-22024-1-git-send-email-
guoqing.ji...@cloud.ionos.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Similar report here on 5.10.0-rc4:
https://www.spinics.net/lists/raid/msg66654.html
I ended up masking the services introduced with 20.04 LTS, and switched back
the crontab.
systemctl mask mdcheck_continue.service mdcheck_continue.timer
mdcheck_start.service mdcheck_start.timer
cat > /etc/cron
Hi Kleber,
I installed it later yesterday, but I won't know until the next resync. This
has been a problem since at least linux 5.4 kernel that shipped with Ubuntu
20.04. I don't think I had these problems on Ubuntu 18.04 LTS, the same
hardware, running the linux-image-generic at that time.
** Attachment added: "screenlog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942935/+attachment/5523575/+files/screenlog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
Public bug reported:
It seems to always occur during an mdcheck/resync, if I am logged in via
SSH it is still somewhat responsive and basic utilities like dmesg will
work. But it apppears any write I/O will hang the terminal and nothing
is written to syslog (presumably because it is blocked).
Be
32 matches
Mail list logo
