From owner-freebsd-fs@FreeBSD.ORG  Sat Mar  6 11:34:32 2004
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3379316A4CE
	for <freebsd-fs@freebsd.org>; Sat,  6 Mar 2004 11:34:32 -0800 (PST)
Received: from happy.cow.org (happy.cow.org [216.130.13.100])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0814243D39
	for <freebsd-fs@freebsd.org>; Sat,  6 Mar 2004 11:34:32 -0800 (PST)
	(envelope-from ravi@cow.org)
Received: by happy.cow.org (Postfix, from userid 1001)
	id D2A6AEB74F; Sat,  6 Mar 2004 14:34:25 -0500 (EST)
Date: Sat, 6 Mar 2004 14:34:25 -0500
From: ravi pina <ravi@cow.org>
To: freebsd-fs@freebsd.org
Message-ID: <20040306193425.GN27094@happy.cow.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Subject: bad blocks
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: ravi@cow.org
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Mar 2004 19:34:32 -0000

hi.

my previous problem involved my raid failed.  i managed
to get some data off of it with much help from various
people.  thank you.

now that i've replaced the disk i created a new raid5
and initted the array.  the new fs completed and i started
copying some data to the array.  i got the following
on a rather large copy:

bad block 1216479232, ino 36090065
pid 5 (syncer), uid 1001 on /stuff: bad block
bad block -560005120, ino 36090065
pid 5 (syncer), uid 1001 on /stuff: bad block
bad block 1482424320, ino 36090065
pid 5 (syncer), uid 1001 on /stuff: bad block
bad block 775028736, ino 36090065
pid 5 (syncer), uid 1001 on /stuff: bad block
bad block 1216479232, ino 36090065
pid 5 (syncer), uid 1001 on /stuff: bad block
bad block -598016000, ino 36090065
pid 5 (syncer), uid 1001 on /stuff: bad block
bad block 1482424320, ino 36090065
pid 5 (syncer), uid 1001 on /stuff: bad block
bad block 775028736, ino 36090065
pid 5 (syncer), uid 1001 on /stuff: bad block
bad block 1216479232, ino 36090065
pid 5 (syncer), uid 1001 on /stuff: bad block
handle_workitem_freeblocks: block count

so i now suspect that there is another failed or failing
disk in the array.  what i'd like to do is create 4
JBODs one for each disk and do some verify on them.  does
a utility exist that will verify the media of the disk
and then map out the bad sectors?  it seems that the 3ware
failed to identify any failed blocks on the init.

thanks again,

-r


--