linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: Freeze after disabling write cache with hdparm -W0 /dev/sda
Date: Fri, 13 Jul 2007 16:45:50 +0900	[thread overview]
Message-ID: <46972DAE.5050503@gmail.com> (raw)
In-Reply-To: <4694CC42.3060808@onelan.co.uk>

Simon Farnsworth wrote:
> Tejun Heo wrote:
>> Simon Farnsworth wrote:
>>> Tejun Heo wrote:
>>>> Simon Farnsworth wrote:
>>>>> Just a thought; is it possible to trigger libata EH from userspace? If
>>>>> so, we could write a small utility to disable write cache, then force EH
>>>>> to detect the change.
>>>> That's automatically done.  libata snoops cache on/off and triggers
>>>> revalidation but you can request manual rescan by echoing "- - -" to
>>>> /sys/class/scsi_host/hostX/scan.
>>>>
>>> Would it be worth changing our code to do "hdparm -W1 /dev/sda && hdparm
>>> -W0 /dev/sda", or would this not show anything. The lack of revalidation
>>> on some drives is what's worrying me a little here.
>> Revalidation happens after cache property is changed successfully.  What
>> happens if you request manual rescan while the drive is not repsponding?
>>
> The 30 second freeze happens when we request manual rescan. We do
> revalidate once the freeze is over, though; dmesg follows:

Can you post dmesg with printk timestamps turned on?

-- 
tejun

  reply	other threads:[~2007-07-13  7:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 10:15 Freeze after disabling write cache with hdparm -W0 /dev/sda Simon Farnsworth
2007-07-11  5:11 ` Tejun Heo
2007-07-11  8:31   ` Simon Farnsworth
2007-07-11  8:36     ` Tejun Heo
2007-07-11  8:54       ` Simon Farnsworth
2007-07-11  8:57         ` Tejun Heo
2007-07-11 12:25           ` Simon Farnsworth
2007-07-13  7:45             ` Tejun Heo [this message]
2007-07-17  8:57               ` Simon Farnsworth
2007-07-11 18:46   ` Mark Lord

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=46972DAE.5050503@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=simon.farnsworth@onelan.co.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).