From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 111441] iscsi fails to attach to targets
Date: Fri, 29 Jan 2016 03:40:42 +0000 [thread overview]
Message-ID: <bug-111441-11613-w4x2QYQuNE@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 #4 from Serguei Bezverkhi <sbezverk@cisco.com> ---
with kernel 4.4.0
lsscsi
[0:0:44:0] enclosu CISCO UCS 240 0809 -
[0:2:0:0] disk LSI MR9261-8i 2.13 /dev/sda
[0:2:1:0] disk LSI MR9261-8i 2.13 /dev/sdb
[3:0:0:2] type? vendor? model? rev? -
[4:0:0:3] type? vendor? model? rev? -
[5:0:0:1] type? vendor? model? rev? -
[6:0:0:4] type? vendor? model? rev? -
[7:0:0:0] type? vendor? model? rev? -
[8:0:0:0] type? vendor? model? rev? -
with kernel 3.10.0-327.4.4
lsscsi
[0:0:44:0] enclosu CISCO UCS 240 0809 -
[0:2:0:0] disk LSI MR9261-8i 2.13 /dev/sda
[0:2:1:0] disk LSI MR9261-8i 2.13 /dev/sdb
[3:0:0:2] disk LIO-ORG san-disk-2 4.0 /dev/sdc
[4:0:0:3] disk LIO-ORG san-disk-3 4.0 /dev/sdd
[5:0:0:1] disk LIO-ORG san-disk-1 4.0 /dev/sde
[6:0:0:4] disk LIO-ORG san-disk-4 4.0 /dev/sdf
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-01-29 3:40 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 [this message]
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
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-w4x2QYQuNE@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).