From owner-freebsd-current Wed Sep 4 0:17:18 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 2B4AD37B400 for ; Wed, 4 Sep 2002 00:17:15 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A73643E42 for ; Wed, 4 Sep 2002 00:17:14 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id HAA28515; Wed, 4 Sep 2002 07:17:08 GMT Date: Wed, 4 Sep 2002 17:24:30 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "D. Rock" Cc: current@FreeBSD.ORG Subject: Re: fsck cannot find superblock In-Reply-To: <3D7511C8.3080306@t-online.de> Message-ID: <20020904171953.I460-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Tue, 3 Sep 2002, D. Rock wrote: > with 'uncommon' block sizes fsck seems to have problems finding the > superblock: > > # newfs -i 10240 -b 4096 -f 512 /dev/ad1d > Reduced frags per cylinder group from 26208 to 26200 to enlarge last cyl group > /dev/ad1d: 409.6MB (838860 sectors) block size 4096, fragment size 512 > using 33 cylinder groups of 12.79MB, 3275 blks, 1312 inodes. > super-block backups (for fsck -b #) at: > 32, 26232, 52432, 78632, 104832, 131032, 157232, 183432, 209632, 235832, > 262032, 288232, 314432, 340632, 366832, 393032, 419232, 445432, 471632, > 497832, 524032, 550232, 576432, 602632, 628832, 655032, 681232, 707432, > 733632, 759832, 786032, 812232, 838432 > # fsck /dev/ad1d > ** /dev/ad1d > Cannot find file system superblock > > LOOK FOR ALTERNATE SUPERBLOCKS? [yn] n fsck_ffs has no problems here with (whole) md disk of the same size. Perhaps I have fixed the problem without noticing. dumpfs or comparison with a non-broken filesystem of the same size might show the problem. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message