From owner-freebsd-stable@FreeBSD.ORG  Thu Nov  3 19:49:14 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: 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 A5DD416A41F
	for <freebsd-stable@freebsd.org>; Thu,  3 Nov 2005 19:49:14 +0000 (GMT)
	(envelope-from taras.savchuk@gmail.com)
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2D68C43D48
	for <freebsd-stable@freebsd.org>; Thu,  3 Nov 2005 19:49:14 +0000 (GMT)
	(envelope-from taras.savchuk@gmail.com)
Received: by wproxy.gmail.com with SMTP id 71so245452wra
	for <freebsd-stable@freebsd.org>; Thu, 03 Nov 2005 11:49:13 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Dgc3mmejQonfSr7ziNrmvIL1mb9LOWC87BgwCIwWq9Rv2maNrj7G+mm1rAhvjQDow8c4B+GHkYjEtatnz3lkEkSozZHzG6XzcxpLiqxWdPRmyQ06oCB4s8J3EsHNx5gnWd4PAjdnvWzfZa84R37zkQ4XWNZGxboOpkJaCEKpEjg=
Received: by 10.65.75.11 with SMTP id c11mr1132024qbl;
	Thu, 03 Nov 2005 11:49:13 -0800 (PST)
Received: by 10.65.160.16 with HTTP; Thu, 3 Nov 2005 11:49:13 -0800 (PST)
Message-ID: <84099c3d0511031149u53fee379of6158584e075d38d@mail.gmail.com>
Date: Thu, 3 Nov 2005 22:49:13 +0300
From: Taras Savchuk <taras.savchuk@gmail.com>
To: Xin LI <delphij@gmail.com>
In-Reply-To: <a78074950511031120r6b51bbedt692b7ed614f0da45@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <84099c3d0511030325q6d1df92ag77310ff1b03a2d15@mail.gmail.com>
	<84099c3d0511030535x400c80f4k7ab7ad1905d8f918@mail.gmail.com>
	<a78074950511031120r6b51bbedt692b7ed614f0da45@mail.gmail.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: May be a bug in fsck [ after super block crash on 5.4-STABLE ]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
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: Thu, 03 Nov 2005 19:49:14 -0000



On 11/3/05, Xin LI <delphij@gmail.com> wrote:
  On 11/3/05, Taras Savchuk <taras.savchuk@gmail.com> wrote:
> My SATA HDD with UFS2 crashed. While checking HDD fsck said, that alterna=
te
> super block at block 32 is not present. In 'man fsck' I saw, that in UFS2=
 =20
> (my file system) alternate super block is usually located in block 160 (F=
or
> UFS1 - in 32). So the question is: why fsck trying to find alternate
> superblock in wrong block for UFS2? I can suppose, that fsck dont know fi=
le =20
> system type (UFS1 or UFS2) while checking, but such assumption seems to b=
e
> wrong.
>
> fsck with '-b 160' optione works well.

I think this is a bug.  You may want to dig into fsck_ffs/setup.c to =20
find out how to solve this...

I'll try, but I'm not a big kernel-hacker. Thank you for answer.