From owner-freebsd-questions Wed Jan 13 12:36:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25494 for freebsd-questions-outgoing; Wed, 13 Jan 1999 12:36:16 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from finsco.com (ns1.finsco.com [216.0.231.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA25449 for ; Wed, 13 Jan 1999 12:36:07 -0800 (PST) (envelope-from billh@finsco.com) Received: from finsco.com by finsco.com (SMI-8.6/SMI-SVR4) id OAA18499; Wed, 13 Jan 1999 14:32:00 -0600 Message-ID: <369D0327.4A83E3D7@finsco.com> Date: Wed, 13 Jan 1999 14:33:43 -0600 From: Bill Hamilton X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Saowanee Saewong CC: freebsd-questions@FreeBSD.ORG Subject: Re: I got a problem with fsck. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had exactly the same problem on my system (2.2.7) a few weeks ago on /var. fsck could not get past it (DIRECTORY CORRUPTED). I eventually had to newfs it, but I didn't lose much since it was a pretty new install. No one could help me, except to say "you gotta restore a backup". Apparently, you are not getting much help either. There is probably a way to edit the fs directly if you had enough info. It's also probably a good way to destroy the rest of your disk. You might first try fsck -b blocknumber. I think you can get alternate superblocks using dumpfs. The first is 32, I think, then there are some others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message