Re: sd 6:0:0:0: [sdb] Unaligned partial completion

2018-09-20 Thread Ted Cabeen
On 06/11/2018 04:08 PM, James Bottomley wrote: On Mon, 2018-06-11 at 14:59 -0700, Ted Cabeen wrote: On 06/11/2018 02:40 PM, James Bottomley wrote: On Mon, 2018-06-11 at 12:20 -0400, Douglas Gilbert wrote: I have also seen Aborted Command sense when doing heavy testing on one or more SAS disks

Re: sd 6:0:0:0: [sdb] Unaligned partial completion

2018-06-13 Thread Ted Cabeen
Will do. It'll be a few weeks, as I have to schedule downtime, but I'll report back my results when it's done. --Ted On 06/11/2018 04:08 PM, James Bottomley wrote: OK, try this: it will print a rate limited warning if it triggers (showing it is this problem) and return ADD_TO_MLQUEUE for all

Re: sd 6:0:0:0: [sdb] Unaligned partial completion

2018-06-11 Thread Ted Cabeen
On 06/11/2018 02:40 PM, James Bottomley wrote: On Mon, 2018-06-11 at 12:20 -0400, Douglas Gilbert wrote: I have also seen Aborted Command sense when doing heavy testing on one or more SAS disks behind a SAS expander. I put it down to a temporary lack of paths available (on the link between the

Re: sd 6:0:0:0: [sdb] Unaligned partial completion

2018-06-11 Thread Ted Cabeen
That makes some sense to me. Sathya, Chaitra, and Suganath, is that a change we should consider making to the MPT Fusion Drivers? --Ted On 06/11/2018 09:20 AM, Douglas Gilbert wrote: I have also seen Aborted Command sense when doing heavy testing on one or more SAS disks behind a SAS

Re: sd 6:0:0:0: [sdb] Unaligned partial completion

2018-06-11 Thread Ted Cabeen
I'm seeing a similar behavior on my system, but across multiple devices on a SAS drive array (front bays on a Supermicro-based system with onboard mpt3sas card). The Sense Key here doesn't show a medium error, and the multiple-drive behavior makes me think it's more likely either a controller