All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bs_lists@aakef.fastmail.fm>
To: michaelc@cs.wisc.edu
Cc: linux-scsi@vger.kernel.org, axboe@kernel.dk,
	Mike Christie <mchristi@redhat.com>,
	Bernd Schubert <bschubert@ddn.com>
Subject: Re: [PATCH] scsi/block: increase flush/sync timeout
Date: Wed, 25 Aug 2010 02:36:35 +0200	[thread overview]
Message-ID: <201008250236.35593.bs_lists@aakef.fastmail.fm> (raw)
In-Reply-To: <1280863560-4747-1-git-send-email-michaelc@cs.wisc.edu>

On Tuesday, August 03, 2010, michaelc@cs.wisc.edu wrote:
> From: Mike Christie <mchristi@redhat.com>
> 
> We have been seeing the flush request timeout with a wide
> range of hardware from tgt+iser to FC targets from a major vendor.
> 
> I did this patch which added a flush timeout:
> http://marc.info/?l=linux-scsi&m=127957359200466&w=2
> 
> A problem with that patch is how to determine what value
> should be set and when you need to set it. You will
> not know that you need to increase until it times out
> and fails, then to figure out what to set it to you
> need to set the timeout and try it out a couple times.
> 
> So this patch just increases the flush/sync cache timeout
> to 2 minutes. In testing, it has taken at most around 60
> seconds to complete the operation, so I thought 120 would
> be safe and not add that long of delay if the device was
> really jammed and needed the scsi eh.

Sorry for my late reply. Doesn't it depend on the device cache how long it 
takes? 120s is should be sufficient for everything I worked with, but then 
there are units out there that that have far more cache. Although I don't know 
if those honor the SYNC_CACHE command. Personally I would prefer the previous 
patch as it allows it to tune it with udev (*). So shouldn't just the previous 
patch be updated to 120s default timeout?


Thanks,
Bernd

PS: I just think it is a bit confusing to have different timeouts in differnt 
directories (/sys/block/sdX/device/timeout and 
/sys/block/sdX/queue/flush_timeout). The patch I have on my disk, which I 
never managed to test and therefore never sent to the list, added it to 
/sys/block/sdX/device.




-- 
Bernd Schubert
DataDirect Networks

      parent reply	other threads:[~2010-08-25  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 19:26 [PATCH] scsi/block: increase flush/sync timeout michaelc
2010-08-04  8:17 ` Boaz Harrosh
2010-08-25  0:36 ` Bernd Schubert [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008250236.35593.bs_lists@aakef.fastmail.fm \
    --to=bs_lists@aakef.fastmail.fm \
    --cc=axboe@kernel.dk \
    --cc=bschubert@ddn.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mchristi@redhat.com \
    --cc=michaelc@cs.wisc.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.