From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Eric.Ayers@intec-telecom-systems.com
Cc: dledford@redhat.com (Doug Ledford),
James.Bottomley@steeleye.com (James Bottomley),
Chris.Roets@compaq.com (Roets Chris),
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Linux Cluster using shared scsi
Date: Tue, 1 May 2001 21:38:26 +0100 (BST) [thread overview]
Message-ID: <E14uguj-0002KC-00@the-village.bc.nu> (raw)
In-Reply-To: <15086.60620.745722.345084@gargle.gargle.HOWL> from "Eric Z. Ayers" at May 01, 2001 01:05:16 PM
> Does this package also tell the kernel to "re-establish" a
> reservation for all devices after a bus reset, or at least inform a
> user level program? Finding out when there has been a bus reset has
> been a stumbling block for me.
You cannot rely on a bus reset. Imagine hot swap disks on an FC fabric. I
suspect the controller itself needs to call back for problem events
next prev parent reply other threads:[~2001-05-01 20:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 13:07 Roets, Chris
2001-05-01 14:45 ` James Bottomley
2001-05-01 16:10 ` Doug Ledford
2001-05-01 17:05 ` Eric Z. Ayers
2001-05-01 20:38 ` Alan Cox [this message]
2001-05-01 20:52 ` James Bottomley
2001-05-01 21:07 ` Eric Z. Ayers
2001-05-01 21:24 ` Alan Cox
2001-05-02 15:20 ` Doug Ledford
2001-05-02 16:37 ` Eddie Williams
2001-05-02 17:20 ` Mike Anderson
2001-05-02 17:50 ` Doug Ledford
2001-05-02 18:55 ` Mike Anderson
2001-05-02 20:31 ` Doug Ledford
2001-05-03 12:53 ` James Bottomley
2001-05-03 13:52 ` James Bottomley
2001-05-02 17:39 ` Max TenEyck Woodbury
2001-05-02 17:47 ` Doug Ledford
2001-05-02 21:03 ` Pavel Machek
2001-05-03 22:32 ` Jonathan Lundell
2001-05-02 21:47 ` Max TenEyck Woodbury
2001-05-02 23:16 ` Doug Ledford
2001-05-03 19:57 ` Eric Z. Ayers
2001-05-04 14:52 ` Eddie Williams
-- strict thread matches above, loose matches on Subject: below --
2001-04-27 15:11 James Bottomley
2001-04-27 13:18 Roets, Chris
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=E14uguj-0002KC-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Chris.Roets@compaq.com \
--cc=Eric.Ayers@intec-telecom-systems.com \
--cc=James.Bottomley@steeleye.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@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: 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
all inboxes | Powered by JetHome®