From: Arne R. <arn...@go...> - 2009-07-23 14:24:51
|
Am Donnerstag, den 23.07.2009, 08:32 +0800 schrieb hank peng: > 2009/7/23 Arne Redlich <arn...@go...>: > > Am Dienstag, den 21.07.2009, 08:45 +0800 schrieb hank peng: > >> Hi, folks: > >> We have a self-built board, CPU is MPC8548 which is powerpc > >> architecture. We want to do pressure test to DDRII DRAM to check if it > >> can work in 533MHz. > >> My idea is to use IET target to export a ramdisk file and then use > >> IOmeter to do continuous test. > >> RAMDISK size is set to 128M when configure my > >> > >> #mkfs.ext3 /dev/ram1 > >> #mount /dev/ram1 /mnt/iscsi > >> #dd if=/dev/zero of=/mnt/iscsi/test bs=1024k count=100 > >> > >> My ietd.conf: > >> Target iqn.2009-07.com.storage:testiscsi.20091001080322 > >> Lun 0 Path=/mnt/iscsi/test,Type=fileio > >> HeaderDigest None,None > >> DataDigest None,None > >> Wthreads 16 > >> > >> #/etc/init.d/iscsi-target start > >> > >> On windows side, I can connect this target and network is in Gigabit > >> enviroment, so pressure is enough. > >> > >> After three hours, IET target crashed with the following messages > >> output on my console: > >> > >> iscsi_trgt: Logical Unit Reset (05) issued on tid:3 lun:0 by > >> sid:4611687354162216963 (Function Complete) > >> iscsi_trgt: write_data(434) error -104 at 0x4000013700000002:1 > >> iscsi_trgt: exit_tx(448) 8240 1 -104 > > > > Was there any other output than this, i.e. a kernel oops? > > > No oops, but system is alive after printing above messages. So in what sense did the IET target crash then? Was the ietd process gone? Arne |