From owner-freebsd-current Fri Mar 31 10:34:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from fbsd.ods.org (fbsd.ods.org [63.236.135.3]) by hub.freebsd.org (Postfix) with SMTP id 4FE2737BFAA for ; Fri, 31 Mar 2000 10:34:41 -0800 (PST) (envelope-from geniusj@ods.org) Received: (qmail 31306 invoked by uid 1000); 31 Mar 2000 18:34:30 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Mar 2000 18:34:30 -0000 Date: Fri, 31 Mar 2000 13:34:30 -0500 (EST) From: Systems Administrator To: Matthew Dillon Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: NFS/Vinum problems In-Reply-To: <200003311752.JAA29716@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is my dmesg output, and btw, sorry.. the perl script was not running on the NFS volume, just regularly on a regular 4.0 box, and it crashed the box (yes, I had login limits set), I was just giving another example of what seems to be some instability in 4.0 under high loads.. Here my dmesg from the raid/nfs server: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Fri Mar 31 00:03:37 EST 2000 geniusj@fbsd4.ods.org:/usr/src/sys/compile/RAID Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 186006596 Hz CPU: IDT WinChip C6 (186.01-MHz 586-class CPU) Origin = "CentaurHauls" Id = 0x541 Stepping = 1 Features=0x8000b5 real memory = 50331648 (49152K bytes) config> en ed0 config> po ed0 0x240 config> ir ed0 5 config> iom ed0 0xd8000 config> f ed0 0 config> q avail memory = 45297664 (44236K bytes) Preloaded elf kernel "kernel" at 0xc036f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc036f09c. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 3.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 eisa0: on isab0 mainboard0: on eisa0 slot 0 isa0: on isab0 ahc0: port 0xf800-0xf8ff mem 0xfedff000-0xfedffff f irq 15 at device 5.0 on pci0 ahc0: Using left over BIOS settings ahc0: aic7855 Single Channel A, SCSI Id=7, 3/255 SCBs ahc1: port 0xf400-0xf4ff mem 0xfedfe000-0xfedfeff f irq 15 at device 6.0 on pci0 ahc1: Using left over BIOS settings ahc1: aic7855 Single Channel A, SCSI Id=7, 3/255 SCBs fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3cf iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA (mono) <16 virtual consoles, flags=0x200> ed0 at port 0x240-0x25f iomem 0xd8000-0xd9fff irq 5 drq 0 on isa0 ed0: address 00:00:c0:00:dc:ba, type SMC8416T (16 bit) Waiting 15 seconds for SCSI devices to settle vinum: loaded da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da5 at ahc1 bus 0 target 5 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da5: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da6 at ahc1 bus 0 target 6 lun 0 da6: Fixed Direct Access SCSI-2 device da6: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da6: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da4 at ahc1 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da4: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da3 at ahc1 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) Mounting root from ufs:/dev/da0s1a cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.032MB/s transfers (4.032MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2048MB (4195116 512 byte sectors: 64H 32S/T 2048C) WARNING: / was not properly dismounted vinum: reading configuration from /dev/da6s1e vinum: updating configuration from /dev/da5s1e vinum: updating configuration from /dev/da4s1e vinum: updating configuration from /dev/da3s1e vinum: updating configuration from /dev/da2s1e vinum: updating configuration from /dev/da1s1e I hope this helps.. and i'll setup crash dumping on raid, thanks for your time On Fri, 31 Mar 2000, Matthew Dillon wrote: > ::Jason DiCioccio > > Another possibility -- could you post your 'dmesg' output? One thing > that NFS does do is severely exercise both the network and the SCSI > device in a concurrent fashion. > > If you happen to be using an NCR SCSI chipset, that could be the cause > of the problem (though I have never in my life seen the panic message > you posted in relation to the NCR cards). > > If you can get the panic regularly then it may be worthwhile trying to > get some more information out of it. If you compile up a kernel with > the DDB option and your console is not running X, then the kernel will > drop into DDB on the console when it panics and allow you to do a > stack 'trace'. You may also be able to then dump the machine by typing > 'panic' manually at the ddb prompt after copying down the trace > information. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message