From owner-freebsd-questions Tue Sep 18 9:22:41 2001 Delivered-To: freebsd-questions@freebsd.org Received: from toblerone.cs.umd.edu (toblerone.cs.umd.edu [128.8.129.39]) by hub.freebsd.org (Postfix) with ESMTP id 7DAFF37B407 for ; Tue, 18 Sep 2001 09:22:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by toblerone.cs.umd.edu (8.9.3/8.9.1) with ESMTP id MAA10483; Tue, 18 Sep 2001 12:22:25 -0400 (EDT) Date: Tue, 18 Sep 2001 12:22:25 -0400 (EDT) From: Aram Khalili To: Ian Dowse Cc: freebsd-questions@freebsd.org Subject: Re: corrupted superblock/fsck problem In-Reply-To: <200109180035.aa44033@salmon.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 18 Sep 2001, Ian Dowse wrote: > The master superblock is at block 16; the one at block 32 is indeed Yikes, I had assumed it starts at block 0. So what did I clobber? The boot block? The /home filesystem isn't bootable ... > Very little information of importance changes in the master > superblock, so there is no need to update the backup copies. Any > summary information can be re-computed by fsck, and most fields > are filesystem parameters that don't change. About the only things > you might want updated in the backup superblocks are the various > settings that can be changed with 'tunefs', and it has the -A option > for that. It doesn't include the count of used/free inodes and blocks in the filesystem (not the bitmap, just the count)? I'm more familiar with ext2, and I think it does. -aram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message