public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 217599] Adaptec 71605z hangs with aacraid: Host adapter abort request after update to linux 6.4.0
Date: Sat, 16 Dec 2023 22:00:15 +0000	[thread overview]
Message-ID: <bug-217599-11613-60h01BnW2q@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217599-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217599

--- Comment #49 from Maxim (leyyyyy@gmail.com) ---
I used 2 raid arrays:

- RAID0 with 8 SATA drives (8x4TB)
- RAID0 with 2 SATA drives (2x16TB)

Both was with LUKS and Ext4/BTRFS (tried both) on that moment.

To reproduce it I just started copying files from one array (2nd one) to
another using some file manager like Midnight Commander.

During copying it can process some amount of data before problem happens and
message appears in dmesg output. When it happens copying becomes slow, all
hangs, and finally the copying is rejected.

btrfs scrub gives similar result, it says that data is corrupt after starting
scanning (maybe 200-300 GB is scanned OK before it happens).

It is single CPU system, I never used multi-socket MB in in such scenarios.

I do not think you need fio, I think you need to move a lot of data to array
(for example big media files, VM images, backup files and so on).

2nd time when I got the same issue was different system, and it is also copying
of data from RAID0 10x1TB SSD to RAID0 6x8TB HDD (LUKS and BTRFS).

--

I do not think it is hardware issue because on old kernels it works fine with
the same settings of the array. If FS is not damaged I can just boot in older
kernel and all will work fine on the same file system. Usually FS will not be
damaged if you not try to repair it by fsck.ext2 using problematic aacraid
driver.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-12-16 22:00 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 22:36 [Bug 217599] New: Adaptec 71605z hangs with aacraid: Host adapter abort request after update to linux 6.4.0 bugzilla-daemon
2023-06-27  1:31 ` [Bug 217599] " bugzilla-daemon
2023-06-27  1:47 ` bugzilla-daemon
2023-06-27  2:11 ` bugzilla-daemon
2023-06-27  2:39 ` [Bug 217599] New: " Bagas Sanjaya
2023-06-27  2:39 ` [Bug 217599] " bugzilla-daemon
2023-06-28  9:38 ` bugzilla-daemon
2023-07-03 17:21 ` bugzilla-daemon
2023-07-22 18:48 ` bugzilla-daemon
2023-07-23 18:03 ` bugzilla-daemon
2023-07-23 18:14 ` bugzilla-daemon
2023-07-27 21:22 ` bugzilla-daemon
2023-07-31 19:04 ` bugzilla-daemon
2023-08-02 13:01 ` bugzilla-daemon
2023-08-03 15:53 ` bugzilla-daemon
2023-09-05 14:57 ` bugzilla-daemon
2023-09-05 16:04 ` bugzilla-daemon
2023-09-07 17:41 ` bugzilla-daemon
2023-09-07 17:45 ` bugzilla-daemon
2023-09-07 21:38 ` bugzilla-daemon
2023-09-07 21:48 ` bugzilla-daemon
2023-09-26  7:36 ` bugzilla-daemon
2023-10-20 11:08 ` bugzilla-daemon
2023-10-25 10:22 ` bugzilla-daemon
2023-10-25 10:23 ` bugzilla-daemon
2023-10-26  7:35 ` bugzilla-daemon
2023-11-11  6:43 ` bugzilla-daemon
2023-11-16  8:45 ` bugzilla-daemon
2023-11-18 14:23 ` bugzilla-daemon
2023-11-18 22:47 ` bugzilla-daemon
2023-11-21  9:54 ` bugzilla-daemon
2023-11-21 13:24   ` James Bottomley
2023-11-21 13:24 ` bugzilla-daemon
2023-11-21 13:30 ` bugzilla-daemon
2023-11-21 13:34 ` bugzilla-daemon
2023-11-21 15:27 ` bugzilla-daemon
2023-11-22 22:18 ` bugzilla-daemon
2023-11-23  8:02 ` bugzilla-daemon
2023-11-23 14:39 ` bugzilla-daemon
2023-11-23 14:58 ` bugzilla-daemon
2023-11-23 17:26 ` bugzilla-daemon
2023-11-24  6:57 ` bugzilla-daemon
2023-11-24  6:58 ` bugzilla-daemon
2023-11-24 12:19 ` bugzilla-daemon
2023-11-28 14:15 ` bugzilla-daemon
2023-12-06 13:52 ` bugzilla-daemon
2023-12-08 17:20 ` bugzilla-daemon
2023-12-09  0:56 ` bugzilla-daemon
2023-12-09 21:13 ` bugzilla-daemon
2023-12-16  4:07 ` bugzilla-daemon
2023-12-16  5:35 ` bugzilla-daemon
2023-12-16 22:00 ` bugzilla-daemon [this message]
2023-12-18  6:58 ` bugzilla-daemon
2023-12-18  7:14 ` bugzilla-daemon
2023-12-18  7:31 ` bugzilla-daemon
2023-12-21  7:49 ` bugzilla-daemon
2023-12-30  0:22 ` bugzilla-daemon
2023-12-30 12:41 ` bugzilla-daemon
2024-01-06 19:38 ` bugzilla-daemon
2024-01-07 10:11 ` bugzilla-daemon
2024-01-07 10:48 ` bugzilla-daemon
2024-01-25  3:07 ` bugzilla-daemon
2024-01-25 18:30 ` bugzilla-daemon
2024-02-01 19:46 ` bugzilla-daemon
2024-02-14 13:11 ` bugzilla-daemon
2024-02-14 14:10 ` bugzilla-daemon
2024-10-13  0:52 ` bugzilla-daemon
2024-10-14  7:29 ` bugzilla-daemon
2024-10-21 22:56 ` bugzilla-daemon
2025-01-02 10:17 ` bugzilla-daemon
2025-01-03  8:27 ` bugzilla-daemon
2025-01-06  4:31 ` bugzilla-daemon
2025-01-06 13:52 ` bugzilla-daemon
2025-01-07  3:33 ` bugzilla-daemon
2025-01-27 21:59 ` bugzilla-daemon
2025-02-03 18:40 ` bugzilla-daemon
2025-07-22  2:33 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-217599-11613-60h01BnW2q@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox