From owner-freebsd-current Mon Oct 5 21:34:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29548 for freebsd-current-outgoing; Mon, 5 Oct 1998 21:34:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29522 for ; Mon, 5 Oct 1998 21:34:49 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost by echonyc.com (8.9.1/8.9.1) with SMTP id AAA10476; Tue, 6 Oct 1998 00:34:43 -0400 (EDT) Date: Tue, 6 Oct 1998 00:34:43 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Doug White cc: current@FreeBSD.ORG Subject: Re: 3.0-981004-BETA observations In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Oct 1998, Doug White wrote: > 1. The disk in it originally had 2.2.1 in dedicated mode installed on it. > I went through sysinstall's 'Express' feature, removing the old > partition and putting a new one on and making a Greg Lehey > Monolithic(tm) layout. At the commit step, for some reason newfs wigged > out on it, reporting: > > newfs: ioctl(WDINFO): cross-device link > newfs: /dev/rwd0s1a: can't rewrite disk label > > Exiting back to the main menu and going through 'express' again worked > fine. Go figure. I've been running into something similar: when newfsing /dev/rsd1f by hand, I get: newfs: ioctl(WDINFO): inappropriate ioctl for device newfs: /dev/rsd1f: can't rewrite disk label And when I run newfs again immediately, same arguments, I don't get the messages. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message