From owner-freebsd-current Wed Sep 4 16:35:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A2B937B400 for ; Wed, 4 Sep 2002 16:35:48 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id ACA1243E65 for ; Wed, 4 Sep 2002 16:35:46 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 5 Sep 2002 00:35:43 +0100 (BST) To: Bruce Evans Cc: Daniel Rock , current@FreeBSD.ORG Subject: Re: fsck cannot find superblock In-Reply-To: Your message of "Thu, 05 Sep 2002 06:24:49 +1000." <20020905053617.Q2728-100000@gamplex.bde.org> Date: Thu, 05 Sep 2002 00:35:37 +0100 From: Ian Dowse Message-ID: <200209050035.aa83853@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020905053617.Q2728-100000@gamplex.bde.org>, Bruce Evans writes: >> * drop support for 4K block sizes completely, but this breaks >> backwards compatibility > >I use patches like the following for the sanity checks: I think there may be other problems that are triggered by using <8k blocks on -current too. Last time I tried 4k blocks (pre-UFS2), the snapshot code would cause a panic when trying to allocate a single 4k block to fit the 8k superblock (the machine then got stuck in a reboot-fsck-panic cycle until interrupted and manually fsck'd). Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message