FUJITA Tomonori wrote:
> I think that it's the initiator issue. Initiators on RHEL5.2 (or something) can't log in too?
okay, with the RH provided initiator drivers I can log in / read / write fine. It turns out that I had two problems: 1st the crc mismatch (which didn't let me log-in) and 2nd a bug in disktest v1.1.12 which didn't let me write to the disk with the -D X:Y option since it opens the file in read-only mode, see below.
Or.
> # ./disktest -PT -T30 -h1 -K1 -B1k -ID /dev/sdf -D 0:100
> | 2009/09/24-23:18:05 | INFO | 4655 | v1.1.12 | /dev/sdf | Balancing percentage between reads and writes
> | 2009/09/24-23:18:05 | START | 4655 | v1.1.12 | /dev/sdf | Start args: -PT -T30 -h1 -K1 -B1k -ID /dev/sdf -D (-N 2000) (-r) (-c) (-p r) (-L 1000)
> | 2009/09/24-23:18:05 | INFO | 4655 | v1.1.12 | /dev/sdf | Starting pass
> | 2009/09/24-23:18:05 | ERROR | 4655 | v1.1.12 | /dev/sdf | Write failed: seek 1, lba 446 (0x1BE), got = -1, asked for = 1024
> # strace -ff ./disktest -PT -T30 -h1 -K1 -B1k -ID /dev/sdf -D 0:100
> pid 4663] open("/dev/sdf", O_RDONLY|O_DIRECT) = 3
> [pid 4663] lseek(3, 552960, SEEK_SET) = 552960
> [pid 4663] write(3, "\0\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"..., 1024) = -1 EBADF (Bad file descriptor)
> [pid 4663] write(1, "| 2009/09/24-23:18:42 | ERROR | "..., 127| 2009/09/24-23:18:42 | ERROR | 4661 | v1.1.12 | /dev/sdf | Write failed: seek 1, lba 1080 (0x438), got = -1, asked for = 1024
> ) = 127
the bug is that the file is opened with O_RDONLY but disktest tries to write... I assume it may be fixed in later versions, I will check.
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
