From owner-freebsd-questions Sun Aug 16 14:14:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24957 for freebsd-questions-outgoing; Sun, 16 Aug 1998 14:14:25 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ziplink.net (relay-0.ziplink.net [206.15.168.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24951 for ; Sun, 16 Aug 1998 14:14:23 -0700 (PDT) (envelope-from lrios@ziplink.net) Received: from mothership (lrios.ziplink.net [206.15.144.221]) by ziplink.net (8.8.7/8.8.7) with SMTP id RAA12355 for ; Sun, 16 Aug 1998 17:13:50 -0400 (EDT) Message-ID: <016301bdc959$6e6f4460$dd900fce@mothership> From: "Luis Rios" To: Subject: File Descriptors on 2.1.5 Machine Date: Sun, 16 Aug 1998 17:04:15 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0160_01BDC937.E6497540" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0160_01BDC937.E6497540 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I recently had a 2.1.5 (upgrading to 2.2.7!) machine reboot due to = problems with a SCSI drive. When I tried to reboot the machine it froze = on fsck of dev sd2 and gave errors of bad file descriptors and excessive = blocks. I did a fsck -y and waited patiently after 20 minutes for fsck = to complete. Fsck managed to clear up lots of erros and boot fine but = I'm getting file descriptor errors when doing ls -la or anything. What = can I do to repair the descriptor tables if so possible? Will dump and = restore restore order to the descriptors? =20 ------=_NextPart_000_0160_01BDC937.E6497540 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I recently had a 2.1.5 (upgrading to = 2.2.7!)=20 machine reboot due to problems with a SCSI drive. When I tried to = reboot=20 the machine it froze on fsck of dev sd2 and gave errors of bad file = descriptors=20 and excessive blocks. I did a fsck -y and waited patiently after = 20=20 minutes for fsck to complete. Fsck managed to clear up lots of = erros and=20 boot fine but I'm getting file descriptor errors when doing ls -la or=20 anything. What can I do to repair the descriptor tables if so = possible?=20 Will dump and restore restore order to the=20 descriptors? =20

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