Date: Wed, 07 Jan 2009 15:27:57 +0200 From: Danny Braniss <danny@cs.huji.ac.il> To: Angelo <nglrossi@gmail.com> Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi client hangs performing I/O on a dead target Message-ID: <E1LKYRx-0000na-VV@kabab.cs.huji.ac.il> In-Reply-To: <6c1e076a0901070247l7c006efajda8fddee84c337a@mail.gmail.com> References: <E1LKUmz-000O18-Kp@kabab.cs.huji.ac.il> <6c1e076a0901070247l7c006efajda8fddee84c337a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> ------=_Part_16620_23870833.1231325237102 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > On Wed, Jan 7, 2009 at 10:33 AM, Danny Braniss <danny@cs.huji.ac.il> wrote: > > > > Hi, > > > > > > I'm experimenting on iscsi; both the target and the initiator are vmware > > > virtual machines and are running 7.0-RELEASE. > > > So far everything works fine except that the client hangs forever (state > > is > > > PHYSWR) if it is accessing (dd if=/dev/zero of=/dev/da0) the device while > > it > > > "dies" (shutdown of the target machine). > > > > > what happens when you bring back the target? > > > > > Is this the expected behaviour? > > > > > yes. > > but maybe it can be 'fixed', I'm concidering adding some kind of timeout > > flag/option. > > > > > I would like to be able to configure a timeout so the command that is > > trying > > > to access the unavailable device fails and I can handle the problem but I > > > can't find anything in iscontrol man pages. > > > > > > Thanks, > > > Angelo > > > _______________________________________________ > > > freebsd-scsi@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > > > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > > > > > > Hi Danny, > > > thanks for your reply. > > when the target comes back it is reconnected properly by the initiator. > > The usage of iscsi I had in mind was an initiator connecting to two targets > and using the two devices as parts of a raid 1 array. > I was expecting that a failure on one of the disks (network down, target > machine down) would be eventually detected and the raid turned to degraded > but still usable. > What happens now to me is that the whole raid device gets unusable for all > the time the target is down. > > As I said before I am just experimenting. I don't know how other > implementations of iscsi initiator work and maybe my idea is just insane :) > I don't know either, the RFC does not mention this case - or maybe I missed it :-) But others have raised the issue, and so it got me thinking, but freebsd likes to panic if a disc goes away, so don't hold your breath for a solution soon. danny > Thanks, > Angelo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1LKYRx-0000na-VV>