From owner-freebsd-current@FreeBSD.ORG  Mon Jan  7 08:29:36 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 5287BE55
 for <current@freebsd.org>; Mon,  7 Jan 2013 08:29:36 +0000 (UTC)
 (envelope-from admin@lissyara.su)
Received: from mx.lissyara.su (mx.lissyara.su [91.227.18.11])
 by mx1.freebsd.org (Postfix) with ESMTP id E9E9F167
 for <current@freebsd.org>; Mon,  7 Jan 2013 08:29:35 +0000 (UTC)
Received: from [79.164.58.122] (port=56393 helo=dc7700p.lissyara.su)
 by mx.lissyara.su with esmtpa (Exim 4.80 (FreeBSD))
 (envelope-from <admin@lissyara.su>) id 1Ts85H-0005MZ-KJ
 for current@freebsd.org; Mon, 07 Jan 2013 12:29:27 +0400
Message-ID: <50EA8766.3020500@lissyara.su>
Date: Mon, 07 Jan 2013 12:29:26 +0400
From: Alex Keda <admin@lissyara.su>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: current@freebsd.org
Subject: Re: fsck problem
References: <201301062315.r06NFgH4065878@chez.mckusick.com>
In-Reply-To: <201301062315.r06NFgH4065878@chez.mckusick.com>
Content-Type: text/plain; charset=windows-1251; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Description: if spam count > 60 - this is spam
X-Spam-Count: 0
X-Descriptions: powered by www.lissyara.su
X-Bounce-ID: mx.lissyara.su
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 08:29:36 -0000

07.01.2013 03:15, Kirk McKusick пишет:
>> Date: Wed, 02 Jan 2013 00:46:53 +0400
>> From: Alex Keda <admin@lissyara.su>
>> To: current@freebsd.org
>> Subject: fsck problem
>>
>> so, whats reason for use SUJ?
>
> SUJ is used to speed up the fsck process. If you have had hard disk
> errors then it is not able to recover and you need to run fsck in the
> old full-fsck way.
>
> It is not necessary to disable the journal. If fsck runs and fails
> it marks the journal as failed so when you rerun fsck it will
> run in the old full-fsck mode. Note that running `fsck -y' is not
> recommended as that says make this filesystem clean no matter what.
> So while you will end up with a clean filesystem, it may be empty
> if you had a bad block in the root directory. Instead you should
> run fsck and read and think about the questions rather than just
> blindly answering them all yes.

it's HDD not have bad blocks - it's hardware RAID10

I run fsck -y more than 3 time, before disable journal.
it's can't fix error, with enabled journal

and, I see it's error not first time.