Hi, friends,
I have test nbd like this:
iometer
|
iscsi initiator ------------------ iscsi target (iet) (Path=/dev/nbd0,
Type=blockio)
------------------ |
windows nbd client ----------- nbd
server
---------------
|
linux
/tmp/testfile
--------------------
linux
with multi worker on iometer, or 512B random write test, the iscsi target stop
the response soon after the test beginning.
report in /var/log/messge is
Logical Unit Reset.....
and I cant use ietadm to show the target information anymore, the command halt
there.
Is this a problem of nbd? replace /dev/nbd0 with a harddisk, like /dev/sdb, the
test works well.
Thanks.
Huang
2007.12.6
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Nbd-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nbd-general
