From owner-freebsd-fs@FreeBSD.ORG Tue Jun 20 21:00:12 2006 Return-Path: X-Original-To: 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 2C93716A505 for ; Tue, 20 Jun 2006 21:00:11 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.245.105.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37CFF43D7D for ; Tue, 20 Jun 2006 21:00:04 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id A5C2531324; Tue, 20 Jun 2006 17:00:01 -0400 (EDT) Date: Tue, 20 Jun 2006 17:00:01 -0400 (EDT) From: Ensel Sharon To: freebsd-fs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: RE: Adaptec 2820sa redux, and possible problems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2006 21:00:12 -0000 Additional tests reveal that an rsync from array0 -> array1 also causes the kernel controller to crash, etc. Both arrays can survive a brutal (big, long, lots of inodes) rsync, and they can even survive it when they are done simultaneously. They just can't survive it to each other (although I was surprised that an rsync over ssh behaved the same as a 'mv' or a 'cp'...) The good news is, it doesn't seem to be a bad card or corrupt memory or anything, since the crash is predictable and non-randomm. All disk caching is turned off in the controller, and the arrays were created with no read or write caching. There is no hardware (disk or controller) caching going on of any kind. Any other information I can provide ? Thanks.