From owner-freebsd-net@FreeBSD.ORG  Wed Apr 11 17:18:14 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id AF061106566B;
	Wed, 11 Apr 2012 17:18:14 +0000 (UTC)
	(envelope-from egrosbein@rdtc.ru)
Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5])
	by mx1.freebsd.org (Postfix) with ESMTP id 14CF38FC08;
	Wed, 11 Apr 2012 17:18:13 +0000 (UTC)
Received: from eg.sd.rdtc.ru (localhost [127.0.0.1])
	by eg.sd.rdtc.ru (8.14.5/8.14.5) with ESMTP id q3BHIBAM060260;
	Thu, 12 Apr 2012 00:18:11 +0700 (NOVT)
	(envelope-from egrosbein@rdtc.ru)
Message-ID: <4F85BCD3.3060900@rdtc.ru>
Date: Thu, 12 Apr 2012 00:18:11 +0700
From: Eugene Grosbein <egrosbein@rdtc.ru>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU;
	rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7
MIME-Version: 1.0
To: =?KOI8-R?Q?=EB=CF=CE=D8=CB=CF=D7_=E5=D7=C7=C5=CE=C9=CA?=
	<kes-kes@yandex.ru>
References: <61227818.20120409213654@yandex.ru> <4F835728.5030809@rdtc.ru>
	<1003395682.20120411200510@yandex.ru>
In-Reply-To: <1003395682.20120411200510@yandex.ru>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 8bit
Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org
Subject: Re: fsck problem FreeBSD 8.3
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2012 17:18:14 -0000

12.04.2012 00:05, Коньков Евгений пишет:
> Здравствуйте, Eugene.
> 
> Вы писали 10 апреля 2012 г., 0:39:52:
> 
> EG> 10.04.2012 01:36, Коньков Евгений пишет:
>>> Hi.
>>>
>>> Apr  9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK
>>> Apr  9 19:51:58 fsck:
>>> Apr  9 19:51:58 fsck:
>>> Apr  9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
>>> Apr  9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG
>>> Apr  9 20:09:22 kernel:
>>>
>>> running manually:
>>> # fsck -y /dev/ad8s1e
>>> ** /dev/ad8s1e (NO WRITE)
> 
> EG> You cannot run fsck on mounted filesystem, unmount it first.
> Why not? fsck can do its job at background, on mounted FS.

It is run in special mode then, you run fsck not that way.

> So I also can run it on mounted FS.

"NO WRITE" signals you that it will not be able to fix any problem it encounters.

> in this case (as I have showed) it do not find any errors.

And if it finds any error on mounted live file system,
that would not mean the error really exists.
Do NOT run fsck on mounted file system, period.

> In any case I have run fsck on this FS when it was dismounted.
> There is no any errors.

So, you need not bother, your file system has been already fixed.

> I think here is only one problem. problem to 'RUN FAST FSCK'

No need to, already.

Eugene Grosbein