Date: Fri, 13 Aug 1999 19:16:46 -0500 From: Karl Denninger <karl@Denninger.Net> To: Randy Bush <randy@psg.com>, FreeBSD SCSI <freebsd-scsi@FreeBSD.ORG> Subject: Re: dump to dlt gets write error Message-ID: <19990813191646.A57450@Denninger.Net> In-Reply-To: <m11FRK1-0008G5C@rip.psg.com>; from Randy Bush on Fri, Aug 13, 1999 at 05:05:17PM -0700 References: <m11FRK1-0008G5C@rip.psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I've seen this kind of stupidity before and you're not going to like the
problem or solution.
Put the DLT on a different SCSI bus (different host adapter) from the disks.
Specifically, separate the fast/wide and narrow SCSI devices.
I've seen both DLTs and other "non-wide" devices have kittens with disks
running fast/wide on the same SCSI bus. It usually manifests itself as
an I/O error on the narrow device - which is exactly what you're getting.
My guess is that the hardware on the narrow (and not-so-fast) device gets
mightily confused by the shorter signal times (even though they're not
aimed at that target) and randomly "freaks out" enough to botch an
operation.
Do you get any kind of DMESG log when the write *fails* (check it) or a
console log of the actual error?
--
--
Karl Denninger (karl@denninger.net) Web: childrens-justice.org
Tired of the broken divorce system in the United States and what it's doing
to our kids? SIGN the online petition for equal parental - and children's -
rights at the above URL. Make a difference in a kid's life today.
Real-time chat now available from the above web page
On Fri, Aug 13, 1999 at 05:05:17PM -0700, Randy Bush wrote:
> asus p2b-ds 2x350mhz, 128mb
> two barracudas
> quantum dlt2000
> 4.0-currnt of 99.04.03
>
> rip.psg.com:/# /do-dump
> ...
> DUMP: Date of this level 0 dump: Fri Aug 13 16:07:11 1999
> DUMP: Date of last level 0 dump: the epoch
> DUMP: Dumping /dev/rccd5c (/usr) to /dev/nrsa0
> DUMP: mapping (Pass I) [regular files]
> DUMP: mapping (Pass II) [directories]
> DUMP: estimated 2951716 tape blocks.
> DUMP: dumping (Pass III) [directories]
> DUMP: dumping (Pass IV) [regular files]
> DUMP: 11.37% done, finished in 0:38
> DUMP: 25.73% done, finished in 0:28
> DUMP: 39.41% done, finished in 0:23
> DUMP: 51.77% done, finished in 0:18
> DUMP: 64.66% done, finished in 0:13
> DUMP: 76.19% done, finished in 0:09
> DUMP: 88.92% done, finished in 0:04
> DUMP: write error 2700020 blocks into volume 1
> DUMP: Do you want to restart?: ("yes" or "no")
>
> usually a LOT more fits on a tape, like four machines more.
>
> i ran the cleaning tape. i tried different tapes from different batches,
> including one that worked in the past. it breaks at different places, but
> always much of the way through that partition.
>
> clues solicited.
>
> randy
>
>
> Copyright (c) 1992-1999 The FreeBSD Project.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> The Regents of the University of California. All rights reserved.
> FreeBSD 4.0-CURRENT #0: Sun Jun 13 16:30:40 PDT 1999
> root@rip.psg.com:/usr/src/sys/compile/RIP-SMP
> Timecounter "i8254" frequency 1193182 Hz
> CPU: Pentium II/Xeon/Celeron (686-class CPU)
> Origin = "GenuineIntel" Id = 0x651 Stepping=1
> Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
> real memory = 134217728 (131072K bytes)
> config> USERCONFIG
> Invalid command or syntax. Type `?' for help.
> config> pnp 1 0 enable os port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5
> config> pnp 1 1 enable os port0 0x200
> config> pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20
> config> quit
> avail memory = 127676416 (124684K bytes)
> Programming 24 pins in IOAPIC #0
> FreeBSD/SMP: Multiprocessor motherboard
> cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000
> cpu1 (AP): apic id: 0, version: 0x00040011,
> at 0xfee00000
> io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
> Preloaded elf kernel "kernel" at 0xc02bc000.
> Preloaded userconfig_script "/kernel.config" at 0xc02bc09c.
> ccd0-5: Concatenated disk drivers
> Probing for devices on PCI bus 0:
> chip0: <Intel 82443BX host to PCI bridge> rev 0x02 on pci0.0.0
> chip1: <Intel 82443BX host to AGP bridge> rev 0x02 on pci0.1.0
> chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.4.0
> chip3: <Intel 82371AB Power management controller> rev 0x02 on pci0.4.3
> ahc0: <Adaptec aic7890/91 Ultra2 SCSI adapter> rev 0x00 int a irq 19 on pci0.6.0
> ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs
> fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 19 on pci0.9.0
> fxp0: Ethernet address 00:a0:c9:df:c8:4e
> bktr0: <BrookTree 878> rev 0x02 int a irq 18 on pci0.10.0
> bti2c0: <bt848 Hard/Soft I2C controller>
> iicbb0: <I2C generic bit-banging driver> on bti2c0
> iicbus0: <Philips I2C bus> on iicbb0 master-only
> iicsmb0: <I2C to SMB bridge> on iicbus0
> smbus0: <System Management Bus> on iicsmb0
> smb0: <SMBus general purpose I/O> on smbus0
> iic0: <I2C general purpose I/O> on iicbus0
> smbus1: <System Management Bus> on bti2c0
> smb1: <SMBus general purpose I/O> on smbus1
> Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, msp3400c stereo.
> Detected a MSP3430G-A1
> Probing for devices on PCI bus 1:
> vga0: <Matrox model 051f graphics accelerator> rev 0x00 int a irq 16 on pci1.0.0
> Probing for PnP devices:
> CSN 1 Vendor ID: CTL00c3 [0xc3008c0e] Serial 0x1fd0a682 Comp ID: PNPb02f [0x2fb0d041]
> pcm1 (SB16pnp <SB16 PnP> sn 0x1fd0a682) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa
> Probing for devices on the ISA bus:
> sc0 on isa
> sc0: VGA color <4 virtual consoles, flags=0x0>
> atkbdc0 at 0x60-0x6f on motherboard
> atkbd0 irq 1 on isa
> psm0 irq 12 on isa
> psm0: model Generic PS/2 mouse, device ID 0
> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
> sio0: type 16550A
> sio1 at 0x2f8-0x2ff irq 3 on isa
> sio1: type 16550A
> pcm0 not probed due to drq conflict with pcm1 at 1
> fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: 1.44MB 3.5in
> wl0 at 0x300-0x30f irq 7 on isa
> wl0: address 08:00:6a:2b:dd:a7, NWID 0xaaaa
> vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
> npx0 on motherboard
> npx0: INT 16 interface
> APIC_IO: Testing 8254 interrupt delivery
> APIC_IO: routing 8254 via pin 2
> wl0 XXX: driver didn't set ifq_maxlen
> Waiting 15 seconds for SCSI devices to settle
> SMP: AP CPU #1 Launched!
> sa0 at ahc0 bus 0 target 6 lun 0
> sa0: <DEC DLT2000 8B37> Removable Sequential Access SCSI-2 device
> sa0: 5.000MB/s transfers (5.000MHz, offset 15)
> changing root device to da0s1a
> da0 at ahc0 bus 0 target 0 lun 0
> da0: <SEAGATE ST34573LW 5702> Fixed Direct Access SCSI-2 device
> da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled
> da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C)
> da1 at ahc0 bus 0 target 1 lun 0
> da1: <SEAGATE ST34573LW 5702> Fixed Direct Access SCSI-2 device
> da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled
> da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C)
> cd0 at ahc0 bus 0 target 4 lun 0
> cd0: <TEAC CD-ROM CD-532S 1.0A> Removable CD-ROM SCSI-2 device
> cd0: 20.000MB/s transfers (20.000MHz, offset 16)
> cd0: Attempt to query device size failed: NOT READY, Medium not present
> cd1 at ahc0 bus 0 target 5 lun 0
> cd1: <YAMAHA CRW4416S 1.0f> Removable CD-ROM SCSI-2 device
> cd1: 8.333MB/s transfers (8.333MHz, offset 31)
> cd1: cd present [140956 x 2048 byte records]
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-scsi" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990813191646.A57450>