From owner-freebsd-scsi Thu Oct 31 10:24:44 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25733 for freebsd-scsi-outgoing; Thu, 31 Oct 1996 10:24:44 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA25728 for ; Thu, 31 Oct 1996 10:24:41 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA04306; Thu, 31 Oct 1996 19:22:10 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA03480; Thu, 31 Oct 1996 19:22:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id TAA16208; Thu, 31 Oct 1996 19:17:20 +0100 (MET) From: J Wunsch Message-Id: <199610311817.TAA16208@uriah.heep.sax.de> Subject: Re: probing scsi bus after boot? To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Thu, 31 Oct 1996 19:17:19 +0100 (MET) Cc: jlk@pavilion.co.uk (Joe Karthauser) Reply-To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) In-Reply-To: <199610311703.RAA08772@deputy.pavilion.co.uk> from Joe Karthauser at "Oct 31, 96 05:03:43 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (Moved to the freebsd-scsi list) As Joe Karthauser wrote: > Is it possible to reprobe the scsi bus after a reboot for allow for > drive swapping? I guess that there must be some support for that in > there somewhere. There's ``scsi -r'', though it used to be horribly broken for quite some time. It worked fine in FreeBSD 1.1.5.1, and started to be ok again in -current of not too long ago (about a month or two). _However_, drive _swapping_ is probably unsupported. I think the sd driver gets royally screwed if you exchange the drive that was present at boot time by one with another total number of blocks later. Even the `od' driver (that is supposed to catch up with such situations) doesn't do it right now, but there's a patch pending in one of the PRs that allows for it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)