From owner-freebsd-questions Tue Aug 28 16:35:36 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-94-248-46.mmcable.com [24.94.248.46]) by hub.freebsd.org (Postfix) with SMTP id 570DB37B401 for ; Tue, 28 Aug 2001 16:35:32 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 96817 invoked by uid 100); 28 Aug 2001 23:35:31 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15244.10947.452112.110319@guru.mired.org> Date: Tue, 28 Aug 2001 18:35:31 -0500 To: "P. U. (Uli) Kruppa" Cc: questions@freebsd.org Subject: Re: BAD SUPER BLOCK In-Reply-To: <106351657@toto.iv> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ 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 P. U. (Uli) Kruppa types: > Micke Josefsson wrote: > > I think this the time to use one of the extra superblocks on the disk. Try > > fsck -b 32 /dev/ad0s2e > > I tried > fsck -b 32 /dev/ad0s2e > but I get an > illegal option --b > and I did not find anything equivalent in # man fsck > By the way: I run FreeBSD -CURRENT . First, unless you've got a good reason - and wanting functionality that's not in -STABLE is NOT a good reason - you shouldn't be running -CURRENT. See section 20.2.1.2 of the handbook for good reasons for the two good reasons for running -CURRENT. The best course of action would be to ask on the -current mail list to see if anyone there is interested in looking into this, as there's a good chance you've stumbled on a bug in the experimental file system snapshot code that's being used in -CURRENT. If you aren't on the -current mail list, you should be - that's even more critical than being on the -stable list if you are tracking -stable, and the latter is pretty much a requirement. Finally, if you just want to fix this to get the system up before going back to -stable, use "fsck_ffs -b 32 /dev/ad0s2e", as fsck has been replaced by something that deals with snapshots and background fscks, and the old fsck is now fsck_ffs. I'd also ask on the -current mail list for advice about taking a file system that may have had snapshots enabled on it back to a -stable kernel. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message