From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 10 11:39:11 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2311616A403 for ; Fri, 10 Nov 2006 11:39:11 +0000 (UTC) (envelope-from freebsd-smp@epcdirect.co.uk) Received: from gunfright.epcdirect.co.uk (gunfright.epcdirect.co.uk [195.10.242.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id B852543D46 for ; Fri, 10 Nov 2006 11:39:10 +0000 (GMT) (envelope-from freebsd-smp@epcdirect.co.uk) Received: from lfarr (l-farr.int.epcdirect.co.uk [192.168.6.200]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 4F9476C883B for ; Fri, 10 Nov 2006 11:39:09 +0000 (GMT) From: "Lawrence Farr" To: Date: Fri, 10 Nov 2006 11:39:10 -0000 Message-ID: <070f01c704bc$d66933d0$0200a8c0@lfarr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 In-Reply-To: <20061017123443.GA1165@koma.free.de> Thread-Index: Acbx6NoSVlT9bBNaSLul0b0ctBDwxgS0uD+w Subject: Areca Weirdness X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2006 11:39:11 -0000 I've got an Areca 12 port card running a 6Tb array which is divided into 2.1Tb chunks at the moment, as it was doing the same with a single 6Tb partition. ad0: 58644MB at ata0-master UDMA100 da0 at arcmsr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 166.666MB/s transfers (83.333MHz, offset 32, 16bit), Tagged Queueing Enabled da0: 2224922MB (4556640256 512 byte sectors: 255H 63S/T 283637C) If I newfs it, and copy data to it, I have no problem initially. If I then try and copy the data on the disk already to a new folder, the machine reboots (it's a remote host with no serial attached currently). When it comes back to life, it mounts, and shows as: /dev/da0 2.1T 343G 1.6T 18% /usr/home/areca1 But is completely empty. Unmounting it and trying to fsck it errors, as does mounting it by hand. [root@nas-2 /home]# fsck -y /dev/da0 ** /dev/da0 Cannot find file system superblock ioctl (GCINFO): Inappropriate ioctl for device fsck_ufs: /dev/da0: can't read disk label [root@nas-2 /home]# mount /dev/da0 mount: /dev/da0 on /usr/home/areca1: incorrect super block Are there any known issues with the driver on AMD64? I had major issues with it on Linux/386 with large memory support (it would behave equally strangely) that went away when I took large memory support out, maybe there are some non 64 bit safe parts common to both?