From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 111441] iscsi fails to attach to targets
Date: Tue, 02 Feb 2016 22:03:46 +0000 [thread overview]
Message-ID: <bug-111441-11613-dlL8kgOuv5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111441-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=111441
--- Comment #12 from Serguei Bezverkhi <sbezverk@cisco.com> ---
HI Mike,
It is working now, it spits alua related error messages but it attaches remote
and local targets, so my OpenStack is back to life. Please let me know if you
plan to commit this fix upstream.
[ 27.579303] scsi 3:0:0:2: Direct-Access LIO-ORG san-disk-2 4.0
PQ: 0 ANSI: 5
[ 27.579797] sd 3:0:0:2: alua: supports implicit and explicit TPGS
[ 27.579932] sd 3:0:0:2: [sdc] 20507809792 512-byte logical blocks: (10.4
TB/9.54 TiB)
[ 27.579975] sd 3:0:0:2: alua: No target port descriptors found
[ 27.579977] sd 3:0:0:2: alua: Attach failed (-22)
[ 27.580640] sd 3:0:0:2: failed to add device handler: -22
[ 27.580897] sd 3:0:0:2: [sdc] Write Protect is off
[ 27.580899] sd 3:0:0:2: [sdc] Mode Sense: 43 00 10 08
[ 27.580922] sd 3:0:0:2: Attached scsi generic sg3 type 0
[ 27.581041] sd 3:0:0:2: [sdc] Write cache: enabled, read cache: enabled,
supports DPO and FUA
[ 27.630156] sd 3:0:0:2: [sdc] Attached SCSI disk
Thank you very much
Serguei
Serguei Bezverkhi,
TECHNICAL LEADER.SERVICES
Global SP Services
sbezverk@cisco.com
Phone: +1 416 306 7312
Mobile: +1 514 234 7374
CCIE (R&S,SP,Sec) - #9527
Cisco.com
Think before you print.
This email may contain confidential and privileged material for the sole use of
the intended recipient. Any review, use, distribution or disclosure by others
is strictly prohibited. If you are not the intended recipient (or authorized to
receive for the recipient), please contact the sender by reply email and delete
all copies of this message.
Please click here for Company Registration Information.
-----Original Message-----
From: Mike Christie [mailto:michaelc@cs.wisc.edu]
Sent: Tuesday, February 02, 2016 3:12 PM
To: Christoph Hellwig <hch@infradead.org>
Cc: Serguei Bezverkhi (sbezverk) <sbezverk@cisco.com>;
bugzilla-daemon@bugzilla.kernel.org; linux-scsi@vger.kernel.org; Hannes
Reinecke <hare@suse.de>
Subject: Re: [Bug 111441] New: iscsi fails to attach to targets
On 02/02/2016 12:09 PM, Christoph Hellwig wrote:
> On Fri, Jan 29, 2016 at 05:32:54PM -0600, Mike Christie wrote:
>> Hey Christoph and Hannes,
>>
>> The dh/alua changes that added this:
>>
>> error = scsi_dh_add_device(sdev);
>> if (error) {
>> sdev_printk(KERN_INFO, sdev,
>> "failed to add device handler: %d\n",
>> error);
>> return error;
>> }
>>
>> to scsi_sysfs_add_sdev are adding a regression.
>>
>> 1. If that fails, then we forget to do device_del before doing the
>> return. My patch in this thread added that back, so we do not see the
>> sysfs oopses anymore. But.....
>
> Ok.
>
>> 2. It looks like in older kernels, we would allow misconfigured
>> targets like this one to still setup devices. Do we want that old behavior back?
>> Should we just ignore the return value from scsi_dh_add_device above?
>> Note that in this case, it is LIO so it can be easily fixed on the
>> target side by just setting it up properly. I do not think other
>> targets would hit this type of issue.
>
> Be liberal in what you accept.. I guess we need to continue allowing
> to connect to these broken targets, but a warning would be useful.
>
> Can you send a patch?
Serguei, can you try the attached patch? Drop the other one I sent.
--
You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-02 22:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 22:51 [Bug 111441] New: iscsi fails to attach to targets bugzilla-daemon
2016-01-29 1:53 ` Mike Christie
2016-01-29 2:13 ` Mike Christie
2016-01-29 2:55 ` Serguei Bezverkhi (sbezverk)
2016-01-29 8:01 ` Michael Christie
2016-01-29 8:25 ` Mike Christie
2016-01-29 12:04 ` Serguei Bezverkhi (sbezverk)
2016-01-29 19:08 ` Michael Christie
2016-01-29 19:11 ` Serguei Bezverkhi (sbezverk)
2016-01-29 19:26 ` Mike Christie
2016-01-29 22:21 ` Serguei Bezverkhi (sbezverk)
2016-01-29 23:32 ` Mike Christie
2016-01-30 7:38 ` Nicholas A. Bellinger
2016-02-01 16:55 ` Mike Christie
2016-02-02 16:41 ` Serguei Bezverkhi (sbezverk)
2016-02-02 22:56 ` Nicholas A. Bellinger
2016-02-02 23:21 ` Serguei Bezverkhi (sbezverk)
2016-02-08 8:01 ` Nicholas A. Bellinger
2016-02-16 19:08 ` Hannes Reinecke
2016-02-27 22:15 ` Nicholas A. Bellinger
2016-02-02 18:09 ` Christoph Hellwig
2016-02-02 20:12 ` Mike Christie
2016-02-02 20:25 ` Serguei Bezverkhi (sbezverk)
2016-02-02 21:54 ` Serguei Bezverkhi (sbezverk)
2016-02-22 0:45 ` Serguei Bezverkhi (sbezverk)
2016-02-22 7:08 ` Hannes Reinecke
2016-02-22 11:36 ` Serguei Bezverkhi (sbezverk)
2016-01-29 3:00 ` [Bug 111441] " bugzilla-daemon
2016-01-29 3:05 ` bugzilla-daemon
2016-01-29 3:32 ` bugzilla-daemon
2016-01-29 3:40 ` bugzilla-daemon
2016-01-29 12:04 ` bugzilla-daemon
2016-01-29 19:11 ` bugzilla-daemon
2016-01-29 22:21 ` bugzilla-daemon
2016-01-30 7:46 ` bugzilla-daemon
2016-02-01 2:13 ` bugzilla-daemon
2016-02-02 16:41 ` bugzilla-daemon
2016-02-02 20:25 ` bugzilla-daemon
2016-02-02 22:03 ` bugzilla-daemon [this message]
2016-02-02 22:56 ` bugzilla-daemon
2016-02-02 23:21 ` bugzilla-daemon
2016-02-08 8:01 ` bugzilla-daemon
2016-02-22 0:45 ` bugzilla-daemon
2016-02-22 7:08 ` bugzilla-daemon
2016-02-22 11:36 ` bugzilla-daemon
2016-02-27 22:15 ` 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-111441-11613-dlL8kgOuv5@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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;
as well as URLs for NNTP newsgroup(s).