Hi Mike, I have a follow up question.
Your notes were very insightful. I was able to recreate exactly what you
said.
I was slightly confused, because iostat counts the operation in its output.
Here's another question: What about other failure scenarios? we talked about
task_set_full and busy,
On 09/02/2011 12:54 PM, iscsi developer man wrote:
Hi Mike, I have a follow up question.
Your notes were very insightful. I was able to recreate exactly what you
said.
I was slightly confused, because iostat counts the operation in its output.
Here's another question: What about
On 08/25/2011 10:28 AM, iscsi developer man wrote:
Hey everyone,
I am writing an iscsi target, and I am working on some experimental
features for dealing with rebuilds.
Right now, I am considering sending back to the initiator a
TASK_SET_FULL SCSI Status, and/or a BUSY SCSI Status, in
Thanks Mike,
So what happens if we return the task set full or the busy status forever?
Does the host get an io error at a certain timeout, does the host silently
return back to the application that the operation has completed
successfully, or does it retry indefinitely?
My concern is that the
On 08/25/2011 05:23 PM, iscsi developer man wrote:
Thanks Mike,
So what happens if we return the task set full or the busy status forever?
Does the host get an io error at a certain timeout, does the host silently
return back to the application that the operation has completed
successfully,
Thanks Mike,
Its good to hear that SCSI BUSY and SCSI Task_Set_Full are both handled
correctly by the linux kernel.
The bug must be in my code then!
I'll look deeper at the wireshark traces.
thanks
iscsi devel man.
On Thu, Aug 25, 2011 at 4:39 PM, Mike Christie micha...@cs.wisc.edu wrote: