From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 12:25:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 1E02B16A420 for ; Thu, 3 Nov 2005 12:25:32 +0000 (GMT) (envelope-from taras.savchuk@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id A659843D5C for ; Thu, 3 Nov 2005 12:25:29 +0000 (GMT) (envelope-from taras.savchuk@gmail.com) Received: by xproxy.gmail.com with SMTP id t10so638966wxc for ; Thu, 03 Nov 2005 04:25:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=jb+a8cWmmOeUKXFw90YH18SFjK8HgiYM/YgC0Pttx5x4z33dDS2ZNK/VqrzhETyWfgTgwzPFRXhIJnkxKukF+C6IlCroiEU23zjP1hhQ5f1WIFRsh3LZxYzVGPBxufJgk6TKeVtnJ9yvExESSPg7K8UGvAdyIUCcrw6haa+jZM0= Received: by 10.65.147.10 with SMTP id z10mr617473qbn; Thu, 03 Nov 2005 04:25:28 -0800 (PST) Received: by 10.65.160.16 with HTTP; Thu, 3 Nov 2005 04:25:28 -0800 (PST) Message-ID: <84099c3d0511030425q3592a288he254cb5f97f976b6@mail.gmail.com> Date: Thu, 3 Nov 2005 15:25:28 +0300 From: Taras Savchuk To: freebsd-current@freebsd.org In-Reply-To: <84099c3d0511030325q6d1df92ag77310ff1b03a2d15@mail.gmail.com> MIME-Version: 1.0 References: <84099c3d0511030325q6d1df92ag77310ff1b03a2d15@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: May be a bug in fsck [ after super block crash on 5.4-STABLE ] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 12:25:32 -0000 On 11/3/05, Taras Savchuk wrote: > > My SATA HDD with UFS2 crashed. While checking HDD fsck said, that > alternate super block at block 32 is not present. In 'man fsck' I saw, th= at > in UFS2 (my file system) alternate super block is usually located in bloc= k > 160 (For UFS1 - in 32). So the question is: why fsck trying to find > alternate superblock in wrong block for UFS2? I can suppose, that fsck do= nt > know file system type (UFS1 or UFS2) while checking, but such assumption > seems to be wrong. PS: With '-b 160' option fsck done work well.