From owner-freebsd-current@FreeBSD.ORG Thu Feb 12 11:42:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53EAE16A4CE for ; Thu, 12 Feb 2004 11:42:51 -0800 (PST) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEB0A43D31 for ; Thu, 12 Feb 2004 11:42:50 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i1CJgfLE007442; Fri, 13 Feb 2004 06:42:41 +1100 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i1CJgbEJ025771; Fri, 13 Feb 2004 06:42:38 +1100 Date: Fri, 13 Feb 2004 06:42:37 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Dima Dorfman In-Reply-To: <20040211235936.GF5681@trit.org> Message-ID: <20040213063855.Y24784@gamplex.bde.org> References: <001a01c3f02f$d8647fe0$2100000a@o8p3f6> <20040211235936.GF5681@trit.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Mdconfig Problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2004 19:42:51 -0000 On Wed, 11 Feb 2004, Dima Dorfman wrote: > Lawrence Farr wrote: > > I've got an odd error with mdconfig, a script which has been > > running on 5.x for months suddenly started giving this error > > > > mdconfig -a -t vnode -f /usr/ftp/pub/FreeBSD/5.2-20040211/floppies/kern.flp > > -u 0 > > mdconfig: ioctl(/dev/mdctl): No such file or directory > > An error that starts with "ioctl(/dev/mdctl)" actually refers to an > error during the processing of the ioctl. Opening the control device > is reported with "open(/dev/mdctl)". The most obvious reason for the > former to fail with ENOENT is that the file you specified using -f > does not exist. Someone should fix them by adding line numbers ;-). Seriously, it can be hard to determine which of several args passed to an ioctl caused the problem, and not mentioniong the ioctl name in error messages doesn't help. Bruce