From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 11:31:38 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 B1E3116A41F for ; Thu, 3 Nov 2005 11:31:38 +0000 (GMT) (envelope-from taras.savchuk@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EE6743D48 for ; Thu, 3 Nov 2005 11:31:38 +0000 (GMT) (envelope-from taras.savchuk@gmail.com) Received: by zproxy.gmail.com with SMTP id 14so151139nzn for ; Thu, 03 Nov 2005 03:31:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=ezGBtuF6vZUDCQiecjF4KiFd/aw8vEeYMArWicJfZYUDDxosTVbhRptsWYLz23HChvBk0J0tlbxBNQ2VupcU3qU2Bm6ixP4N+Lq5PsG/39tvl+d91IOyQD5J4qqbdD+8bY7HDc7qggOfxUuFqvotT6hKQdgK7f2xdqkfVxPJA2k= Received: by 10.65.100.10 with SMTP id c10mr576713qbm; Thu, 03 Nov 2005 03:25:07 -0800 (PST) Received: by 10.65.160.16 with HTTP; Thu, 3 Nov 2005 03:25:07 -0800 (PST) Message-ID: <84099c3d0511030325q6d1df92ag77310ff1b03a2d15@mail.gmail.com> Date: Thu, 3 Nov 2005 14:25:07 +0300 From: Taras Savchuk To: freebsd-current@freebsd.org MIME-Version: 1.0 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: 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 11:31:38 -0000 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, that in UFS2 (my file system) alternate super block is usually located in block 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 dont know file system type (UFS1 or UFS2) while checking, but such assumption seems to be wrong.