Adjusting subject, because there are some MD3000i users and engineers on
the list that can also help.
On 12/14/2010 02:47 AM, Aviad Raviv wrote:
Hi,
I searched the mailing list and have not found an answer to my question, so
i'm sorry for the double post if this has been answered before.
I have setup a multipathing iSCSI initiator on Lenny into a Dell
MD3000i storage device.
The full instructions of how i did it are on my wiki:
http://hotfortech.wikispaces.com/How+To+Configure+iSCSI+initiator+in+debian+lenny+server
(this
is not self promotion, just a clarification aid).
The thing is that i keep getting the "Buffer I/O error" on the console as
can be seen here:
http://hotfortech.wikispaces.com/file/view/open-iscsi1.png/187956001/open-iscsi1.png
Because i have read on another mailing thread that upgrading the
kernel/iscsi package
What is the kernel version (uname -a)?
I think we would need more of the /var/log/messages to make sure, but I
think this is expected.
MD3000i boxes have 1 controller that can execute IO and one that cannot
execute READ/WRITE IO until a special command is sent. In older kernels,
layers like the partition scanning and udev and hal would send down IO
to those disabled paths and we would see IO errors like in your link.
In newer kernels we have device handler modules (for MD3000i you would
want scsi_dh_rdac (so do "modprobe scsi_dh_rdac" and then lsmod to see
if it is there)) that will detect if the path is not active and if so it
will either not send the IO or it will not print a error message since
we expect the IO to fail.
I do not think the iscsi tools package will make a difference here.
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
