Date: Sat, 27 Jun 1998 22:06:44 +0200 (CEST) From: hans@artcom.de (Hans Huebner) To: tege@matematik.su.se Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/6964: Problems with cam-980520 code in FreeBSD-stable Message-ID: <m0yq1FE-0002C8C@mail.artcom.de> In-Reply-To: <199806231730.KAA00895@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199806231730.KAA00895@freefall.freebsd.org> you write: >From: Torbjorn Granlund <tege@matematik.su.se> >To: Stefan Esser <se@freebsd.org> >Cc: Subject: Re: kern/6964: Problems with cam-980520 code in FreeBSD-stable >Date: Tue, 23 Jun 1998 19:20:19 +0200 > > (probe17:ncr0:0:1:0): COMMAND FAILED (6 ff) @f07ea200 > > (probe16:ncr0:0:1:0): COMMAND FAILED (6 ff) @f07ea800 > > (probe15:ncr0:0:0:0): COMMAND FAILED (6 ff) @f07eae00 This is (also) caused by wired-down disk devices which are not available. I regularily configure my SCSI disks to be wired down to specific device names, which results in one such message per unavailable disk. This might not be the right place to start a discussion, but anyway: When will we switch to SCSI device names which correspond to the SCSI bus numbers / SCSI ID of the drive? All commercial Unix vendors do this, and it is the right thing to do. Disk device names get horribly messed if you have a machine with many busses and many drives. Only that Windows NT suffers from the drive letter mixup sickness does not mean that FreeBSD should do so as well. -Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0yq1FE-0002C8C>