Date: Wed, 14 Apr 1999 16:01:57 -0700 (PDT) From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) To: gibbs@narnia.plutotech.com Cc: scsi@FreeBSD.ORG Subject: Re: timed out while idle? Message-ID: <199904142301.QAA60472@silvia.hip.berkeley.edu> In-Reply-To: <199904142037.OAA13777@narnia.plutotech.com> (gibbs@narnia.plutotech.com) References: <199904142037.OAA13777@narnia.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com> * That's not entirely true. The device will come back if it transitions * through final close (e.g you umount -f all filesystems referencing * it). Ooh. I'll try that next time. Thanks. * Further, the code that usually causes the disk pack to be * invalidated is in cam_periph.c:cam_periph_error() where a selection * timeout causes us to receive an ENXIO error. I believe that * invalidating the pack is the correct thing to do since we have no * way of determining if the media or device are the same, but that we should * be retrying things like selection timeouts in a more sane fashion so * that invalidations are a rarity. No, I think that's fine. I could have pulled a disk and put in another one. Not doing anything with it until all references to it are closed sounds like a sensible thing to do. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904142301.QAA60472>