From owner-freebsd-scsi Sun May 10 23:07:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17531 for freebsd-scsi-outgoing; Sun, 10 May 1998 23:07:15 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (mothra.kralizec.net.au [203.15.68.22] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17509 for ; Sun, 10 May 1998 23:07:04 -0700 (PDT) (envelope-from andrew@zeta.org.au) Received: from gurney.reilly.home (d84.syd2.zeta.org.au [203.26.11.84]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA10981 for ; Mon, 11 May 1998 16:00:41 +1000 Received: (from andrew@localhost) by gurney.reilly.home (8.8.8/8.8.5) id PAA01593 for freebsd-scsi@FreeBSD.org; Mon, 11 May 1998 15:27:03 +1000 (EST) From: Andrew Reilly Message-Id: <199805110527.PAA01593@gurney.reilly.home> Date: Mon, 11 May 1998 15:27:03 +1000 (EST) Subject: Do 2k sectors work on od in 2.2-STABLE? To: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've noticed a bit of ctm traffic updating the SCSI subsystem in 2.2-STABLE recently, so I thought I'd give the 640M media another go in my Fujitsu MO drive. The boot scan says: (FreeBSD 2.2.6-STABLE #0: Mon May 11 09:52:07 EST 1998 root@gurney.reilly.home:/usr/src/sys/compile/GURNEY : ahc0:6:0): "FUJITSU M2513A 1300" type 7 removable SCSI 2 od0(ahc0:6:0): Optical 606MB (310352 2048 byte sectors) od0(ahc0:6:0): with approximate 151 cyls, 64 heads, and 32 sectors/track fdisk od0 says: ******* Working on device /dev/rod0 ******* parameters extracted from in-core disklabel are: cylinders=151 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=151 heads=64 sectors/track=32 (2048 blks/cyl) Media sector size is 2048 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 1, size 309247 (603 Meg), flag 80 beg: cyl 0/ sector 2/ head 0; end: cyl 150/ sector 32/ head 63 So seemingly something is going on, but disklabel is still my stumbling block: disklabel od0 disklabel: ioctl DIOCGDINFO: Invalid argument disklabel -w -r od0 auto disklabel: ioctl DIOCSDINFO: No space left on device I'm still not 100% clear about slices, so I thought I'd try: disklabel -w -r od0s4 auto disklabel: ioctl DIOCGDINFO: Invalid argument The latter is at least a different error message than I had received earlier, but it still doesn't look like things will fly. ---> Having failed to create a file system, my fall-back position was always going to be to just use these as a SCSI sack of blocks, for backup programs. To my dismay, though, even dd can't talk to it properly. It's pretty obvioius that only 2k transactions work: dd if=/dev/rod0s4 of=/devnull bs=512 count=1 dd: /dev/rod0s4: Input/output error dd if=/dev/rod0s4 of=/devnull bs=1024 count=1 dd: /dev/rod0s4: Input/output error dd if=/dev/rod0s4 of=/devnull bs=2048 count=1 1+0 records in 1+0 records out 2048 bytes transferred in 0.015324 secs (133647 bytes/sec) however dd seems to calculate the device capacity by multiplying the number of blocks available by DEV_BSIZE, and then dividing this by secsiz. Consequently, it seems to only be able to talk to about 150M of the drive: dd if=/dev/rod0s4 of=/dev/null bs=2048 dd: /dev/rod0s4: Input/output error 77311+0 records in 77311+0 records out 158332928 bytes transferred in 207.976010 secs (761304 bytes/sec) Does anyone know why dd is doing this, and what I can do about it? Shouldn't it have been able to read a little over 600000 2k blocks? Thanks in advance for suggestions, -- Andrew "The steady state of disks is full." -- Ken Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message