From: Mike Christie <mikenc@us.ibm.com> To: device-mapper development <dm-devel@redhat.com> Cc: Arjan van de Ven <arjan@infradead.org>, "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>, "linux-hotplug-devel@lists.sourceforge.net" <linux-hotplug-devel@lists.sourceforge.net>, "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org> Subject: Re: [dm-devel] Re: [ANNOUNCE] multipath-tools-0.3.4 Date: Tue, 26 Oct 2004 10:52:25 -0700 [thread overview] Message-ID: <417E8ED9.7070506@us.ibm.com> (raw) In-Reply-To: <20041025210304.GH3714@marowsky-bree.de> Lars Marowsky-Bree wrote: > On 2004-10-25T11:38:43, christophe.varoqui@free.fr wrote: > > >>In fact all the sg stuff I use is done with the SG_IO ioctl (see >>libcheckers/*.c) But somehow, it doesn't work as expected. I don't >>remember how exactly it failed in my tests but it did ... I remembered >>receiving bad path status and experiencing blocked checkers. > > > Can you please clarify the error you saw? I didn't experience that yet > with the SG_IO ioctl(). > I think it was because of this bug http://marc.theaimsgroup.com/?l=linux-scsi&m=108617935710955&w=2 If you are using qla2xxx and you unplug the cable, the qlogic driver will return did_not_connect in the host byte. If you used the block layer sg io code you will then not get the host bytes returned to you, and the checker will always think the patch is back up. > Sincerely, > Lars Marowsky-Brée <lmb@suse.de> > ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
WARNING: multiple messages have this Message-ID (diff)
From: Mike Christie <mikenc@us.ibm.com> To: device-mapper development <dm-devel@redhat.com> Cc: Arjan van de Ven <arjan@infradead.org>, "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>, "linux-hotplug-devel@lists.sourceforge.net" <linux-hotplug-devel@lists.sourceforge.net>, "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org> Subject: Re: [dm-devel] Re: [ANNOUNCE] multipath-tools-0.3.4 Date: Tue, 26 Oct 2004 17:52:25 +0000 [thread overview] Message-ID: <417E8ED9.7070506@us.ibm.com> (raw) In-Reply-To: <20041025210304.GH3714@marowsky-bree.de> Lars Marowsky-Bree wrote: > On 2004-10-25T11:38:43, christophe.varoqui@free.fr wrote: > > >>In fact all the sg stuff I use is done with the SG_IO ioctl (see >>libcheckers/*.c) But somehow, it doesn't work as expected. I don't >>remember how exactly it failed in my tests but it did ... I remembered >>receiving bad path status and experiencing blocked checkers. > > > Can you please clarify the error you saw? I didn't experience that yet > with the SG_IO ioctl(). > I think it was because of this bug http://marc.theaimsgroup.com/?l=linux-scsi&m\x108617935710955&w=2 If you are using qla2xxx and you unplug the cable, the qlogic driver will return did_not_connect in the host byte. If you used the block layer sg io code you will then not get the host bytes returned to you, and the checker will always think the patch is back up. > Sincerely, > Lars Marowsky-Brée <lmb@suse.de> > ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id\x12065&opÌk _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-10-26 17:52 UTC|newest] Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-25 0:24 [ANNOUNCE] multipath-tools-0.2.9 christophe varoqui 2004-09-25 0:24 ` christophe varoqui 2004-10-06 9:22 ` [ANNOUNCE] multipath-tools-0.3.0 christophe.varoqui 2004-10-06 9:22 ` christophe.varoqui 2004-10-06 9:50 ` [dm-devel] " Lars Marowsky-Bree 2004-10-06 9:50 ` Lars Marowsky-Bree 2004-10-06 10:18 ` christophe.varoqui 2004-10-06 10:18 ` christophe.varoqui 2004-10-11 12:00 ` Lars Marowsky-Bree 2004-10-11 12:00 ` Lars Marowsky-Bree 2004-10-11 12:31 ` christophe.varoqui 2004-10-11 12:31 ` christophe.varoqui 2004-10-07 20:01 ` Dave Olien 2004-10-07 20:01 ` Dave Olien 2004-10-08 12:49 ` christophe.varoqui 2004-10-08 12:49 ` christophe.varoqui 2004-10-11 11:50 ` [ANNOUNCE] multipath-tools-0.3.1 christophe.varoqui 2004-10-11 11:50 ` christophe.varoqui 2004-10-12 18:35 ` Dave Olien 2004-10-12 18:35 ` Dave Olien 2004-10-17 14:03 ` multipath-tools-0.3.2 christophe varoqui 2004-10-17 14:03 ` multipath-tools-0.3.2 christophe varoqui 2004-10-20 10:46 ` [ANNOUNCE] multipath-tools-0.3.3 christophe.varoqui 2004-10-20 10:46 ` christophe.varoqui 2004-10-24 22:14 ` [ANNOUNCE] multipath-tools-0.3.4 christophe varoqui 2004-10-24 22:14 ` christophe varoqui 2004-10-25 8:22 ` Arjan van de Ven 2004-10-25 8:22 ` Arjan van de Ven 2004-10-25 9:38 ` christophe.varoqui 2004-10-25 9:38 ` christophe.varoqui 2004-10-25 10:39 ` Douglas Gilbert 2004-10-25 10:39 ` Douglas Gilbert 2004-10-25 21:03 ` [dm-devel] " Lars Marowsky-Bree 2004-10-25 21:03 ` Lars Marowsky-Bree 2004-10-26 17:52 ` Mike Christie [this message] 2004-10-26 17:52 ` Mike Christie 2004-10-26 10:06 ` [ANNOUNCE] multipath-tools-0.3.5 christophe.varoqui 2004-10-26 10:06 ` christophe.varoqui 2004-11-01 17:08 ` [ANNOUNCE] multipath-tools-0.3.6 christophe varoqui 2004-11-01 17:08 ` christophe varoqui 2004-11-11 23:10 ` [ANNOUNCE] multipath-tools-0.3.7 christophe varoqui 2004-11-11 23:10 ` christophe varoqui 2004-11-25 14:55 ` [ANNOUNCE] multipath-tools-0.3.8 christophe varoqui 2004-11-25 14:55 ` christophe varoqui 2004-12-05 15:43 ` [ANNOUNCE] multipath-tools-0.3.9 christophe varoqui 2004-12-05 15:43 ` christophe varoqui 2004-12-12 17:20 ` [ANNOUNCE] multipath-tools-0.4.0 christophe varoqui 2004-12-12 17:20 ` christophe varoqui 2004-12-12 18:08 ` ISCSI Guy 2004-12-12 18:55 ` ISCSI Ming Zhang 2004-12-12 21:07 ` ISCSI Guy 2004-12-12 21:12 ` ISCSI Ming Zhang 2004-12-20 16:01 ` [ANNOUNCE] multipath-tools-0.4.1 christophe varoqui 2004-12-20 16:01 ` christophe varoqui 2005-01-23 23:03 ` [ANNOUNCE] multipath-tools-0.4.2 christophe varoqui 2005-01-23 23:03 ` christophe varoqui 2005-03-19 14:27 ` [ANNOUNCE] multipath-tools-0.4.3 christophe varoqui 2005-03-19 14:27 ` christophe varoqui 2005-04-24 22:26 ` [ANNOUNCE] multipath-tools-0.4.4 christophe varoqui 2005-04-24 22:26 ` christophe varoqui 2005-04-25 9:28 ` Lars Marowsky-Bree 2004-12-21 22:02 [dm-devel] [ANNOUNCE] multipath-tools-0.4.1 Caushik, Ramesh 2004-12-21 22:02 ` Caushik, Ramesh 2004-12-21 23:03 ` christophe varoqui 2004-12-22 1:09 ` christophe varoqui 2004-12-21 23:19 ` christophe varoqui 2004-12-22 1:26 ` christophe varoqui 2004-12-22 19:26 Caushik, Ramesh 2004-12-22 19:26 ` Caushik, Ramesh 2004-12-22 19:45 ` christophe varoqui 2004-12-22 21:52 ` christophe varoqui 2004-12-22 21:05 James.Smart 2004-12-22 21:05 ` James.Smart 2004-12-22 21:23 ` christophe varoqui 2004-12-22 23:30 ` christophe varoqui 2004-12-22 21:54 Caushik, Ramesh 2004-12-22 21:54 ` Caushik, Ramesh 2004-12-23 13:28 ` Christoph Hellwig 2004-12-23 13:28 ` Christoph Hellwig 2004-12-23 12:19 James.Smart 2004-12-23 12:19 ` James.Smart
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=417E8ED9.7070506@us.ibm.com \ --to=mikenc@us.ibm.com \ --cc=arjan@infradead.org \ --cc=dm-devel@redhat.com \ --cc=linux-hotplug-devel@lists.sourceforge.net \ --cc=linux-raid@vger.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.