2011-05-22 20:39, Richard Elling wrote:
This means that the target closed the connection because there was
already a task in progress.
Likely this was the retry after the timeout. By default, these
timeouts are quite long, so by now
performance is already terrible.
I'm not sure if you ca
comment below...
On May 22, 2011, at 8:31 AM, Jim Klimov wrote:
> Hi all,
>
> As I wrote before, I have a "dpcool" implemented as an iSCSI
> device stored in a volume of my physical "pool". When there
> are many operations, such as attempts to destroy a dataset
> (which leads to many small IOs
Hi all,
As I wrote before, I have a "dpcool" implemented as an iSCSI
device stored in a volume of my physical "pool". When there
are many operations, such as attempts to destroy a dataset
(which leads to many small IOs in my config), the iSCSI
device is 100% busy for hours, latencies can grow t
