I haven't tried reproducing in a VM; it requires quite high io load
across many drives to reproduce reliably on my desktop
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2023497
Title:
The RAID6 setup is:
dm-integrity on every drive, no journalling, with ~10 spinning drives and 2 SSDs
RAID1 across the two dm-integrity devices backed by SSDs
RAID6 across the 10 dm-integrity devices backed by spinning drives, with
--write-journal set to the raid1 SSD integrity device
--
You rec
In case it ends up mattering, here's how I set up the dm-integrity
devices:
$ integritysetup format /dev/sda1 --sector-size 4096 --integrity-no-
journal --journal-size=1 --buffer-sectors=8 --interleave-sectors=8192
--
You received this bug notification because you are a member of Kernel
Packages
The hard lock is very reproducible without the OEM kernel. It's only
after switching to the OEM kernel that I was able to get a stack trace
though. I'd for a long time suspected hardware failure, but I think I've
ruled that out for the below reasons and because I've tried many
different hardware co
The machine is unresponsive after this, so apport-collect cannot be
used.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
Hi there,
When running using the md dirty stripe journal (mdadm --create --write-
journal) I get a machine hard lockup w
Public bug reported:
Hi there,
When running using the md dirty stripe journal (mdadm --create --write-
journal) I get a machine hard lockup when under heavy i/o load. The
issue only occurs when the i/o is going through the md device.
After hooking up a serial console, after upgrading my Jammy in
6 matches
Mail list logo
