From owner-freebsd-fs@FreeBSD.ORG Sat Feb 2 19:31:00 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C61616A419 for ; Sat, 2 Feb 2008 19:31:00 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 82BC913C45B for ; Sat, 2 Feb 2008 19:30:59 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A456B.dip.t-dialin.net [84.154.69.107]) (authenticated bits=0) by tower.berklix.org (8.13.6/8.13.6) with ESMTP id m12JEnIB060054; Sat, 2 Feb 2008 19:14:50 GMT (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m12JGf28003191; Sat, 2 Feb 2008 20:16:41 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m12JGUjN049706; Sat, 2 Feb 2008 20:16:36 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200802021916.m12JGUjN049706@fire.js.berklix.net> To: Martin Cracauer In-reply-to: <20080201172214.GA55957@cons.org> References: <20080201172214.GA55957@cons.org> Comments: In-reply-to Martin Cracauer message dated "Fri, 01 Feb 2008 12:22:14 -0500." Date: Sat, 02 Feb 2008 20:16:30 +0100 From: "Julian H. Stacey" Cc: freebsd-fs@freebsd.org Subject: Re: fsck and mount disagree on whether superblocks are usable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2008 19:31:00 -0000 Martin Cracauer wrote: > This is not an emergency but I find it odd. Mount and fsck agree on > whether superblocks are usable. Mount can mount readonly, but fsck > can use neither the primary superblock nor the alternatives. > > 32 is not a file system superblock Just in case, You know secondary block on newer FSs moved from 32 ? Ref man fsck_ufs -b Use the block specified immediately after the flag as the super block for the file system. An alternate super block is usually located at block 32 for UFS1, and block 160 for UFS2. -- Julian Stacey. BSD Unix Linux Net Consultant, Munich. http://berklix.com