From owner-freebsd-stable@FreeBSD.ORG  Thu Jul  1 23:34:25 2004
Return-Path: <owner-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 1B80016A4CE
	for <freebsd-stable@freebsd.org>;
	Thu,  1 Jul 2004 23:34:25 +0000 (GMT)
Received: from devbiol.bg.biology.uwo.ca (devbiol.bg.biology.uwo.ca
	[129.100.68.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 654C743D41
	for <freebsd-stable@freebsd.org>;
	Thu,  1 Jul 2004 23:34:24 +0000 (GMT)	(envelope-from vzhurov@uwo.ca)
Received: from [192.168.8.31] ([192.168.8.31])	(authenticated bits=0)
	i61NWLvs001050	for <freebsd-stable@freebsd.org>;
	Thu, 1 Jul 2004 19:32:26 -0400 (EDT)	(envelope-from vzhurov@uwo.ca)
Message-ID: <40E49F0B.5010005@uwo.ca>
Date: Thu, 01 Jul 2004 19:32:27 -0400
From: Vladimir Zhurov <vzhurov@uwo.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040618
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
References: <40DEDCD2.3020606@uwo.ca>
	<20040628172309.D43333@carver.gumbysoft.com> <40E31C35.9020307@uwo.ca>
	<20040630190707.T66769@carver.gumbysoft.com>
In-Reply-To: <20040630190707.T66769@carver.gumbysoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: 
 Re: dscheck(#ar/2): negative b_blkno error on FreeBSD-4.10-STABLE
 - SOLVED
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
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: Thu, 01 Jul 2004 23:34:25 -0000

Thank you for suggestions.

Finally, I have solved the problem.

It was in fact hardware failure. One of the drives in array failed 
(despite the "no error found" verdict of WD DLG utility). I discovered 
it by deleting array and initializing drives individually.

But it raises another question. Obviously fsck was right reporting 
errors, atacontrol and WD DLG were wrong reporting that everything was 
fine (I am not sure that atacontrol is designed to detect such errors 
anyway), but how would one figure out which drive failed in such a case 
without actually going into complete re-formating of array?

Vlad.