From owner-freebsd-current@FreeBSD.ORG Wed Feb 11 15:59:38 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 24DCF16A4D2 for ; Wed, 11 Feb 2004 15:59:38 -0800 (PST) Received: from catalina.nimone.com (pat1.gonim.com [66.161.18.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BF0A43D1D for ; Wed, 11 Feb 2004 15:59:38 -0800 (PST) (envelope-from dima@trit.org) Received: from ajax.nimone.com (ajax.nimone.com [192.168.168.100]) by catalina.nimone.com (Postfix) with ESMTP id B7B9036C81; Wed, 11 Feb 2004 23:59:37 +0000 (UTC) Received: (from dima@localhost) by ajax.nimone.com (8.11.6+Sun/8.10.2) id i1BNxbW06304; Wed, 11 Feb 2004 23:59:37 GMT X-Authentication-Warning: ajax.nimone.com: dima set sender to dima@trit.org using -f Date: Wed, 11 Feb 2004 23:59:36 +0000 From: Dima Dorfman To: Lawrence Farr Message-ID: <20040211235936.GF5681@trit.org> References: <001a01c3f02f$d8647fe0$2100000a@o8p3f6> <20040211165140.2C24515809@gunfright.epcdirect.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040211165140.2C24515809@gunfright.epcdirect.co.uk> User-Agent: Mutt/1.4i X-PGP-Key: 69FAE582 (http://www.trit.org/~dima/dima.asc) X-PGP-Fingerprint: B340 8338 7DA3 4D61 7632 098E 0730 055B 69FA E582 X-Mailman-Approved-At: Thu, 12 Feb 2004 05:25:00 -0800 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: Wed, 11 Feb 2004 23:59:38 -0000 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. Hope this helps, Dima.