taskqueue timeout

[Matthew Dillon]

:...
:>     and see if the problem reoccurs with just two drives.
:
:... I knew that was going to come up... my response is "I worked so hard 
:to get this system with ZFS all configured *exactly* how I wanted it".
:
:To test, I'm going to flip to 30 as per Matthews recommendation, and see 
:how far that takes me. At this time, I'm only testing by backing up one 
:machine on the network. If it fails, I'll clock the time, and then 
:'reformat' with two drives.
:
:Is there a technical reason this may work better with only two drives?
:
:Is there anyone interested to the point where remote login would be helpful?
:
:Steve

    This issue is vexing a lot of people.

    Setting the timeout to 30 will not effect performance, but it will
    cause a 30 second delay in recovery when (if) the problem occurs.
    i.e. when the disk stalls it will just sit there doing nothing for
    30 seconds, then it will print the timeout message and try to recover.

    It occurs to me that it might be beneficial to actually measure the
    disk's response time to each request, and then graph it over a period
    of time.  Maybe seeing the issue visually will give some clue as to the
    actual cause.

					-Matt
					Matthew Dillon 
					<dillon at backplane.com>