From owner-freebsd-current Sun Oct 24 8:53:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 4437A150BF for ; Sun, 24 Oct 1999 08:53:32 -0700 (PDT) (envelope-from dennis.glatting@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id IAA10457 for ; Sun, 24 Oct 1999 08:53:28 -0700 (PDT) Date: Sun, 24 Oct 1999 08:53:28 -0700 (PDT) From: Dennis Glatting To: freebsd-current@freebsd.org Subject: Strangeness with vinum 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 I just want to document some strangeness I see with vinum, in case it has been noticed before but not identified, or someone knows a cure. I have a Dell XPS D333 with two Adaptec 2940 Ultra SCSI adapters, one assigned to fast things and the other to slow things, generally. On the slow adapter I have two SEAGATE ST43400N disks I placed under vinum. Below is my config file. drive a device /dev/da3e drive b device /dev/da4e volume vol1 plex org striped 16k sd length 2777m drive a sd length 2777m drive b When I run "iozone -aR" against the volume the entire disks subsystem seems to take a pause from time to time when the file sizes get large (>= 32 MB). By this I mean the pause encompasses both disk controllers. Specifically, if I enter a command in a window, such as "ls," against a disk on the fast controller and my cwd is on that controller too, then there is a big delay before the disk is listed, on the order of 5-10 seconds. My PATH variable does not include any devices on the slow controller. The window system still runs fine as does the network. Strange. Below is my dmesg. Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-STABLE #23: Sat Sep 25 08:27:04 PDT 1999 root@btw:/ExternalDisk/FreeBSD-btw-3.x/src/sys/compile/BTW Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 333346563 Hz CPU: Pentium II/Xeon/Celeron (333.35-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping = 0 Features=0x183f9ff real memory = 402653184 (393216K bytes) avail memory = 388628480 (379520K bytes) Preloaded elf kernel "kernel" at 0xc02fa000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 on pci0.7.3 xl0: <3Com 3c905-TX Fast Etherlink XL> rev 0x00 int a irq 10 on pci0.13.0 xl0: Ethernet address: 00:60:08:b0:3d:a6 xl0: autoneg complete, link status good (half-duplex, 10Mbps) xl1: <3Com 3c905B-TX Fast Etherlink XL> rev 0x64 int a irq 9 on pci0.14.0 xl1: Ethernet address: 00:50:04:d2:9f:c6 xl1: autoneg complete, link status good (half-duplex, 10Mbps) ahc0: rev 0x00 int a irq 3 on pci0.15.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 11 on pci0.16.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: vga0: rev 0x21 int a irq 9 on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model IntelliMouse, device ID 3 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wst0: Drive empty, readonly, reverse, qfa, ecc, 512b wst0: Max speed=600Kb/s, Transfer limit=52 blocks, Buffer size=728 blocks ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 256 packets/entry by default IP Filter: initialized. Default = pass all, Logging = enabled Waiting 15 seconds for SCSI devices to settle sa0 at ahc1 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C) da2 at ahc0 bus 0 target 12 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C) cd0 at ahc1 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: cd present [326045 x 2048 byte records] changing root device to da0s1a da4 at ahc1 bus 0 target 2 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da4: 2777MB (5688447 512 byte sectors: 255H 63S/T 354C) da3 at ahc1 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2777MB (5688447 512 byte sectors: 255H 63S/T 354C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 4095MB (8388314 512 byte sectors: 255H 63S/T 522C) vinum: loaded vinum: reading configuration from /dev/da4e vinum: updating configuration from /dev/da3e xl0: promiscuous mode enabled vinum: CONFIGURATION OBLITERATED vinum: drive a is up vinum: drive b is up vinum: vol1.p0.s0 is up vinum: vol1.p0.s1 is up vinum: vol1.p0 is up vinum: vol1 is up vinum: vol1.p0 is up -- Dennis Glatting Copyright (c) 1999 Software Munitions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message