From owner-freebsd-current  Wed May 19  0:41: 5 1999
Delivered-To: freebsd-current@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id 80A9F14D6A
	for <current@FreeBSD.ORG>; Wed, 19 May 1999 00:40:54 -0700 (PDT)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA31851;
	Wed, 19 May 1999 17:40:50 +1000
Date: Wed, 19 May 1999 17:40:50 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199905190740.RAA31851@godzilla.zeta.org.au>
To: bde@zeta.org.au, sheldonh@uunet.co.za
Subject: Re: MFS still hosed
Cc: current@FreeBSD.ORG, Jos.Backus@nl.origin-it.com,
	luoqi@watermarkgroup.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> >dumping to dev (0, 131089), offset 524288
>> >dump device bad
>> 
>> The dev_t changes obfuscated it by printing it in %d format instead of
>> as part of the dev number in [0x]%x format.
>
>So you reckon that whatever problem is making it imp[ossible for me to
>take dumps, it was present before the dev_t changes and I should be
>looking elsewhere?

"dump device bad" is printed for d_dump() returning ENXIO, which is
fairly unambiguous.  The new wd driver's d_dump would return ENODEV,
so you must be using the old wd driver.  The old wd_driver's d_dump
only returns ENXIO when the drive doesn't exist or has never been
opened or is not labeled.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message