From owner-freebsd-stable@FreeBSD.ORG  Mon May 15 12:51:39 2006
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 313F216A420;
	Mon, 15 May 2006 12:51:39 +0000 (UTC)
	(envelope-from nvass@teledomenet.gr)
Received: from matrix.teledomenet.gr (dns1.teledomenet.gr [213.142.128.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 97D3443D45;
	Mon, 15 May 2006 12:51:37 +0000 (GMT)
	(envelope-from nvass@teledomenet.gr)
Received: from [192.168.1.71] ([192.168.1.71])
	by matrix.teledomenet.gr (8.12.10/8.12.10) with ESMTP id k4FCpaEY029687;
	Mon, 15 May 2006 15:51:36 +0300
From: Nikos Vassiliadis <nvass@teledomenet.gr>
To: freebsd-stable@freebsd.org
Date: Mon, 15 May 2006 15:48:22 +0300
User-Agent: KMail/1.9.1
References: <20060515120057.GA4759@lordcow.org>
In-Reply-To: <20060515120057.GA4759@lordcow.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-7"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200605151548.23090.nvass@teledomenet.gr>
Cc: gareth <bsd@lordcow.org>, stable@freebsd.org
Subject: Re: fsck
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: Mon, 15 May 2006 12:51:42 -0000

On Monday 15 May 2006 15:00, gareth wrote:
> hi, this box has had far too many hard reboots, but can anyone shed some
> light on whether this's inconsistent? i boot into single user mode,

 everything is mounted read-only, 

> run fsck and fix all the partitions. rerunning fsck shows no more problems.
> mounting the filesystems and running fsck shows no problems. but when
> i reboot into normal mode,

 where everything is mounted read-write for normal use

> and run fsck on these 2 particular partitions: 
> (and rebooting into single user mode again doesn't help).
>

You cannot fsck a read-write mounted filesystem. The kernel is using it and
will be in a state where fsck will think it has errors. Umount the filesystem
first, check it then. Álternatively you can snapshot it, and fsck -n the_snapshot

HTH, Nikos