From owner-freebsd-current Wed Jul 31 13:16:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22606 for current-outgoing; Wed, 31 Jul 1996 13:16:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA22601 for ; Wed, 31 Jul 1996 13:16:24 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02705; Wed, 31 Jul 1996 13:14:50 -0700 From: Terry Lambert Message-Id: <199607312014.NAA02705@phaeton.artisoft.com> Subject: Re: DEVFS broken by last devsw_add_generic()/bdevvp() changes To: peter@spinner.DIALix.COM (Peter Wemm) Date: Wed, 31 Jul 1996 13:14:50 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <199607281624.AAA01851@spinner.DIALix.COM> from "Peter Wemm" at Jul 29, 96 00:24:05 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It seems the last set of changes to the devsw creation routines and the > subsequent bdevvp() change has broken ffs_mount when trying to mount the > root filesystem on at least scsi disks. > > The "new" bdevvp() is returning 0, and ffs_mount is not checking it before > passing it onto ffs_mountfs. > > This might be because of the slice code not knowing whether or not it's > using the compatabilty slices or not, or simply because nothing has accessed > the slices in the first place to cause the slice code to create the > initial nodes in devfs. If an I/O is out of range on a wd, the wd strategy returns an error. If an I/O is out of range on an sd or od, the strategy does not error (there is a "goto done;" without an error being set). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.