Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Feb 2004 06:42:37 +1100 (EST)
From:      Bruce Evans <bde@zeta.org.au>
To:        Dima Dorfman <dima@trit.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Mdconfig Problem
Message-ID:  <20040213063855.Y24784@gamplex.bde.org>
In-Reply-To: <20040211235936.GF5681@trit.org>
References:  <001a01c3f02f$d8647fe0$2100000a@o8p3f6> <20040211235936.GF5681@trit.org>

index | next in thread | previous in thread | raw e-mail

On Wed, 11 Feb 2004, Dima Dorfman wrote:

> Lawrence Farr <bsd-current@epcdirect.co.uk> 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


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040213063855.Y24784>