public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Xingui Yang <yangxingui@huawei.com>,
	liyihang9@huawei.com, yanaijie@huawei.com
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxarm@huawei.com, prime.zeng@huawei.com,
	liuyonglong@huawei.com, kangfenglong@huawei.com,
	liyangyang20@huawei.com, f.fangjian@huawei.com,
	xiabing14@h-partners.com
Subject: Re: [PATCH v3 1/3] scsi: hisi_sas: Enable force phy when SATA disk directly connected
Date: Thu, 20 Feb 2025 17:35:38 +0000	[thread overview]
Message-ID: <4bf89b6c-8730-4ae8-8b26-770b2aab2c13@oracle.com> (raw)
In-Reply-To: <20250220130546.2289555-2-yangxingui@huawei.com>

On 20/02/2025 13:05, Xingui Yang wrote:

-john.garry@huawei.com (this has not worked in over 2 years ...)

> the SAS controller determines the disk to which I/Os are delivered based
> on the port id in the DQ entry when SATA disk directly connected.
> 
> When many phys were disconnected immediately and connected again during
> I/O sending and port id of phys were changed and used by other link, I/O
> may be sent to incorrect disk and data inconsistency on the SATA disk may


So is the disk reported gone (from libsas point-of-view) after you 
unplug? If not, why not?

Thanks,
John

  reply	other threads:[~2025-02-20 17:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 13:05 [PATCH v3 0/3] scsi: hisi_sas: Fixed IO error caused by port id not updated Xingui Yang
2025-02-20 13:05 ` [PATCH v3 1/3] scsi: hisi_sas: Enable force phy when SATA disk directly connected Xingui Yang
2025-02-20 17:35   ` John Garry [this message]
2025-02-21  1:59     ` yangxingui
2025-02-24  8:29       ` John Garry
2025-02-24  9:36         ` yangxingui
2025-02-24 12:21           ` John Garry
2025-02-24 13:12             ` yangxingui
2025-02-24 17:34               ` John Garry
2025-02-25  1:48                 ` yangxingui
2025-02-25  8:19                   ` John Garry
2025-02-25  9:35                     ` yangxingui
2025-02-26  8:57                       ` John Garry
2025-02-27  8:33                         ` yangxingui
2025-03-04  9:48                           ` John Garry
2025-03-05  8:16                             ` yangxingui
2025-03-05 16:15                               ` John Garry
2025-03-06  1:44                                 ` yangxingui
2025-03-10 13:09                     ` yangxingui
2025-03-10 17:45                       ` John Garry
2025-03-11  1:53                         ` yangxingui
2025-03-12  9:44                         ` yangxingui
2025-03-12 11:19                           ` John Garry
2025-02-20 13:05 ` [PATCH v3 2/3] scsi: libsas: Move sas_put_device() to libsas.h Xingui Yang
2025-02-21  2:36   ` Jason Yan
2025-02-20 13:05 ` [PATCH v3 3/3] scsi: hisi_sas: Fixed IO error caused by port id not updated Xingui Yang

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=4bf89b6c-8730-4ae8-8b26-770b2aab2c13@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=f.fangjian@huawei.com \
    --cc=jejb@linux.ibm.com \
    --cc=kangfenglong@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=liyangyang20@huawei.com \
    --cc=liyihang9@huawei.com \
    --cc=martin.petersen@oracle.com \
    --cc=prime.zeng@huawei.com \
    --cc=xiabing14@h-partners.com \
    --cc=yanaijie@huawei.com \
    --cc=yangxingui@huawei.com \
    /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