From owner-freebsd-stable@FreeBSD.ORG  Tue Nov 30 07:00:15 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 58EEE16A4CE
	for <freebsd-stable@freebsd.org>;
	Tue, 30 Nov 2004 07:00:15 +0000 (GMT)
Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au
	[211.29.132.186])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 86C9443D68
	for <freebsd-stable@freebsd.org>;
	Tue, 30 Nov 2004 07:00:14 +0000 (GMT)
	(envelope-from PeterJeremy@optushome.com.au)
Received: from cirb503493.alcatel.com.au
	(c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229])
	iAU70C3c022942
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 30 Nov 2004 18:00:12 +1100
Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au
	[127.0.0.1])iAU70BxP061912;	Tue, 30 Nov 2004 18:00:12 +1100 (EST)
	(envelope-from pjeremy@cirb503493.alcatel.com.au)
Received: (from pjeremy@localhost)iAU70BDp061911;
	Tue, 30 Nov 2004 18:00:11 +1100 (EST)	(envelope-from pjeremy)
Date: Tue, 30 Nov 2004 18:00:11 +1100
From: Peter Jeremy <PeterJeremy@optushome.com.au>
To: Michael Nottebrock <michaelnottebrock@gmx.net>
Message-ID: <20041130070010.GX79646@cirb503493.alcatel.com.au>
References: <200411282144.56438.michaelnottebrock@gmx.net>
	<20041128210746.GN32181@gsmx07.alcatel.com.au>
	<200411282225.36617.michaelnottebrock@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200411282225.36617.michaelnottebrock@gmx.net>
User-Agent: Mutt/1.4.2i
cc: freebsd-stable@freebsd.org
Subject: Re: help! bad filesystem summary trashes system
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Nov 2004 07:00:15 -0000

On Sun, 2004-Nov-28 22:25:29 +0100, Michael Nottebrock wrote:
>> Have you tried telling fsck to use an alternate super block (-b option)?
>
>I found an alternate superblock at 128, but using it gives the same error.

That's not promising but you could try one of the other alternates.
Assuming you didn't specify any non-standard options when you (or
sysinstall) created that partition, running "newfs -N <device>" will
report all the alternate superblocks.

>> If it's just a glitch that's affected the primary super block, this
>> should work.  If the in-core data got corrupted and has been written to
>> all the superblocks, you might need to play with a filesystem editor.
>
>Can you suggest such an editor (and possibly give some hints what exactly to 
>do with it)? 

Unfortunately, no.  I thought there was something in ports but I can't find
it now.  You might need to write something yourself :-(.

-- 
Peter Jeremy