From owner-freebsd-questions Thu Dec 30 6:31:34 1999 Delivered-To: freebsd-questions@freebsd.org Received: from fw.intechsoft.net (okcds1-blk1-hfc-0251-d1db0faa.rdc1.ok.coxatwork.com [209.219.15.170]) by hub.freebsd.org (Postfix) with ESMTP id 08AD214E5C for ; Thu, 30 Dec 1999 06:31:29 -0800 (PST) (envelope-from internal@intechsoft.net) Received: from wkbruce ([192.168.1.12]) by fw.intechsoft.net (8.9.3/8.9.3) with SMTP id IAA17198; Thu, 30 Dec 1999 08:31:25 -0600 (CST) (envelope-from internal@intechsoft.net) Message-ID: <008801bf52d2$8d92c840$0c01a8c0@wkbruce> From: "Bruce DeVault" To: "Bruce DeVault" , References: <006b01bf52d2$3793dbf0$0c01a8c0@wkbruce> Subject: Re: bad file descriptor Date: Thu, 30 Dec 1999 08:31:25 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0085_01BF52A0.42C169C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0085_01BF52A0.42C169C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sorry, forgot to mention one additional thing, it also has a bad file = descriptor on /etc/vinum.conf... Do I need to run fsck? I'm kind of afraid to. All the drives are = mounted and all my data's there, or appears to be. Bruce DeVault InTech Software ----- Original Message -----=20 From: Bruce DeVault=20 To: freebsd-questions@FreeBSD.ORG=20 Sent: Thursday, December 30, 1999 8:29 AM Subject: bad file descriptor Yesterday (12-29-1999) morning I cvsup'd and make world the same as i = do every week or so with 3.4-STABLE, and upon reboot after installing my = new kernel (GENERIC, with the added options for IPDIVERT, IPFIREWALL, = IPFIREWALL_VERBOSE and SOFTUPDATES) I saw: dev_mkdb: rwd2: Bad file descriptor dev_mkdb: wd2a: Bad file descriptor ...and on and on for twenty more lines or so... The machine in question has three IDE drives and an IDE CD-ROM, as = well as an ATA-2940U/UW SCSI controller and a SCSI tape drive. Two of = the IDE drives are striped RAID-0 with vinum. What gives? Didn't used to do this... (?) ------=_NextPart_000_0085_01BF52A0.42C169C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Sorry, forgot to mention one additional = thing, it=20 also has a bad file descriptor on /etc/vinum.conf...
 
Do I need to run fsck?  I'm kind = of afraid=20 to.  All the drives are mounted and all my data's there, or appears = to=20 be.
 
Bruce DeVault
InTech = Software
----- Original Message -----
From:=20 Bruce=20 DeVault
To: freebsd-questions@FreeBSD.ORG =
Sent: Thursday, December 30, = 1999 8:29=20 AM
Subject: bad file = descriptor

Yesterday (12-29-1999) morning I = cvsup'd and make=20 world the same as i do every week or so with 3.4-STABLE, and upon = reboot after=20 installing my new kernel (GENERIC, with the added options for = IPDIVERT,=20 IPFIREWALL, IPFIREWALL_VERBOSE and SOFTUPDATES) I saw:
 
dev_mkdb: rwd2: Bad file = descriptor
dev_mkdb: wd2a: Bad file = descriptor
...and on and on for twenty more = lines or=20 so...
 
The machine in question has three IDE = drives and=20 an IDE CD-ROM, as well as an ATA-2940U/UW SCSI controller and a SCSI = tape=20 drive.  Two of the IDE drives are striped RAID-0 with = vinum.
 
What gives?  Didn't used to do = this...=20 (?)
------=_NextPart_000_0085_01BF52A0.42C169C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message