Bug#1104677: marked as done (mkfs.ext4: Error formatting raid array partition on kernel 6.1.0-34-amd64)

2025-05-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 May 2025 18:02:26 + with message-id and subject line Bug#1104460: fixed in linux 6.1.137-1 has caused the Debian Bug report #1104460, regarding mkfs.ext4: Error formatting raid array partition on kernel 6.1.0-34-amd64 to be marked as done. This means that you claim

Bug#1104677:

2025-05-06 Thread Mohammadreza Nasrabadi
I checked the diffs and saw the mentioned commit between v6,1,134 and v6.1.135. The v6.1.134 was stable and without bug and v6.1.135 was the buggy version. I also installed unstab

Bug#1104677: mkfs.ext4: Error formatting raid array partition on kernel 6.1.0-34-amd64

2025-05-05 Thread Salvatore Bonaccorso
Control: forcemerge 1104460 -1 Hi, On Mon, May 05, 2025 at 04:12:23PM +0330, Mohammadreza Nasrabadi wrote: > Yeah I also checked the kernel logs and saw kernel panic logs. I will > attach the kernel logs on this email. Another fact I saw, was that today > (Monday, the first day of the week) the f

Processed: Re: Bug#1104677: mkfs.ext4: Error formatting raid array partition on kernel 6.1.0-34-amd64

2025-05-05 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 1104460 -1 Bug #1104460 [src:linux] linux-image-6.1.0-34-powerpc64le: Discard broken with RAID10: BUG: kernel tried to execute user page (0) - exploit attempt? Bug #1104677 [src:linux] mkfs.ext4: Error formatting raid array partition on kernel 6.1.0

Bug#1104677:

2025-05-05 Thread Mohammadreza Nasrabadi
Yeah I also checked the kernel logs and saw kernel panic logs. I will attach the kernel logs on this email. Another fact I saw, was that today (Monday, the first day of the week) the fstream systemd timer is started and during the operation on the RAID device, the system load grows and stuck up and