From owner-freebsd-hackers Thu Jun 19 14:39:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20958 for hackers-outgoing; Thu, 19 Jun 1997 14:39:53 -0700 (PDT) Received: from pobox.com (ott-on1-22.netcom.ca [207.181.90.86]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20950 for ; Thu, 19 Jun 1997 14:39:49 -0700 (PDT) Received: (from brianc@localhost) by pobox.com (8.8.5/8.8.5) id RAA01531; Thu, 19 Jun 1997 17:39:00 -0400 (EDT) Message-ID: <19970619173858.39930@pobox.com> Date: Thu, 19 Jun 1997 17:38:58 -0400 From: Brian Campbell To: freebsd-hackers@FreeBSD.org Subject: fs recovery Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk What's the normal sequence of steps to recover from a corrupted filesystem? It appears the first 64-inodes are "screwy" (according to fsdb). After that, things look reasonable. I used fsdb to look at the first 150k inodes and found an expected mixture of directories and inodes. Is there an easy way to recreate my root directory and link some of these directories (presumably the ones whose parent was inode 2? how do I find that out?) into the root? Or, failing that ... I have a backup from about a week ago. Is there a tool to scan what's left of the filesystem for anything more recent? Help! ;-)