From owner-freebsd-current@FreeBSD.ORG Fri Apr 30 13:54:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0225716A4CE for ; Fri, 30 Apr 2004 13:54:46 -0700 (PDT) Received: from fed1rmmtao04.cox.net (fed1rmmtao04.cox.net [68.230.241.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id B160A43D31 for ; Fri, 30 Apr 2004 13:54:45 -0700 (PDT) (envelope-from sahafeez@zaphodb.org) Received: from [192.168.64.100] (really [68.96.79.160]) by fed1rmmtao04.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040430205428.BUXO8743.fed1rmmtao04.cox.net@[192.168.64.100]> for ; Fri, 30 Apr 2004 16:54:28 -0400 Mime-Version: 1.0 (Apple Message framework v613) In-Reply-To: <56E610F6-9AE6-11D8-A3A5-003065F1EE08@zaphodb.org> References: <56E610F6-9AE6-11D8-A3A5-003065F1EE08@zaphodb.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <9226739E-9AE8-11D8-A3A5-003065F1EE08@zaphodb.org> Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org From: Sean Hafeez Date: Fri, 30 Apr 2004 13:54:28 -0700 X-Mailer: Apple Mail (2.613) Subject: Re: 5.2.1 Vinum/Firewire/Crash under load? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Apr 2004 20:54:46 -0000 ok. so i booted the system without the fw drives on. and things worked fine. i was going to kill the vinum and newfs each drive and try to move data to them. the system crashed just the same. i think the issue is with the fw code. -sean On Apr 30, 2004, at 1:38 PM, Sean Hafeez wrote: > Just built a new system. > > AMD2000+, 512MB RAM, 2 NIC (re0, vr0), Firewire with 4 drives. > > > fwohci0: port 0xc800-0xc87f mem 0xe0061000-0xe00617ff irq > 11 at device 12.0 on pci0 > fwohci0: OHCI version 1.0 (ROM=1) > fwohci0: No. of Isochronous channel is 8. > fwohci0: EUI64 00:11:06:00:00:00:ab:27 > fwohci0: Phy 1394a available S400, 3 ports. > fwohci0: Link S100, max_rec 2 bytes. > fwohci0: max_rec 2 -> 2048 > firewire0: on fwohci0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:11:06:00:ab:27 > sbp0: on firewire0 > fwohci0: Initiate bus reset > fwohci0: BUS reset > fwohci0: node_id=0xc800ffc2, gen=1, CYCLEMASTER mode > firewire0: 3 nodes, maxhop <= 2, cable IRM = 2 (me) > firewire0: bus manager 2 (me) > > .... > > da0 at sbp0 bus 0 target 0 lun 0 > da0: Fixed Simplified Direct Access > SCSI-4 device > da0: 50.000MB/s transfers, Tagged Queueing Enabled > da0: 156334MB (320173056 512 byte sectors: 255H 63S/T 19929C) > da1 at sbp0 bus 0 target 0 lun 1 > da1: Fixed Simplified Direct Access > SCSI-4 device > da1: 50.000MB/s transfers, Tagged Queueing Enabled > da1: 156334MB (320173056 512 byte sectors: 255H 63S/T 19929C) > da2 at sbp0 bus 0 target 1 lun 0 > da2: Fixed Simplified Direct Access > SCSI-4 device > da2: 50.000MB/s transfers, Tagged Queueing Enabled > da2: 156334MB (320173056 512 byte sectors: 255H 63S/T 19929C) > da3 at sbp0 bus 0 target 1 lun 1 > da3: Fixed Simplified Direct Access > SCSI-4 device > da3: 50.000MB/s transfers, Tagged Queueing Enabled > da3: 156334MB (320173056 512 byte sectors: 255H 63S/T 19929C) > > > I setup Vinum as RAID5. I did a full INIT of all the drives. > > After that was done I newfs'd it and the system crash - rebooted - no > logs. > > Hum. I had messed with the kernel trying to get RAIDFRAME working 1st > so I nuked the system and started over with GENERIC. > > OK, set everything up again. newfs works. Mount the drive. Everything > seems OK. > > make install samaba .... and start copying over 80gb of files. Bam! > Reboots. No Logs. > > Hum. OK. Just thru hoops - tried 5.1 and 5.2 - same issues. > > Tried Win2K server - maid a RAID5 with the Windows tools. Copied > everything over fine - been up and running for hours.. > > Anyone point me to want to look at or what files I could post? > > Thanks, > Sean > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" >