linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
	James.Bottomley@SteelEye.com, hmh@hmh.eng.br,
	linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] sd: implement stop_on_shutdown
Date: Sat, 20 Jan 2007 04:50:11 -0500	[thread overview]
Message-ID: <45B1E5D3.90101@pobox.com> (raw)
In-Reply-To: <45B18AE2.3010503@gmail.com>

Tejun Heo wrote:
> Darrick J. Wong wrote:
>> Tejun Heo wrote:
>>> sd doesn't stop (unload head) on shutdown.  This behavior is necessary
>>> for multi initiator cases.  Unloading head by powering off stresses
>>> the drive and sometimes produces distinct clunking noise which
>>> apparently disturbs users considering multiple reports on different
>>> distributions.  halt(8) usually puts the drives to sleep prior to
>>> shutdown but the implementation is fragile and it doesn't work with
>>> sleep-to-disk.
>> I wonder if this sort of thing (cache flush + spin down) is the sort of
>> thing that ought to be done to near-line storage at suspend time too,
>> though one would want allow_restart = 1 before doing such a thing.
> 
> For ATA, it's currently being done inside libata proper (a bit ugly).
> It would be nice to have those implemented at sd layer but I wonder how
> useful it's going to be for actual SCSI devices.  Do people actually
> suspend using SCSI?  If it's useful at the SCSI layer, I can implement
> and test it with SATA devices here.

There is always the open question for multi-initiator SCSI devices, as 
to who "owns" the SCSI device.  Some devices should be suspended/stopped 
when the machine is suspended/stopped, others not.

	Jeff




  reply	other threads:[~2007-01-20  9:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 17:01 [PATCH] sd: implement stop_on_shutdown Tejun Heo
2007-01-19 23:34 ` Douglas Gilbert
2007-01-20  3:18   ` Tejun Heo
2007-01-21 22:47     ` Stefan Richter
2007-01-19 23:42 ` Darrick J. Wong
2007-01-20  3:22   ` Tejun Heo
2007-01-20  9:50     ` Jeff Garzik [this message]
2007-01-20  9:59       ` Tejun Heo
2007-01-20 14:39       ` James Bottomley
2007-01-20 14:39     ` James Bottomley
2007-02-05  9:43       ` Tejun Heo
2007-02-05 14:55         ` James Bottomley

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=45B1E5D3.90101@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=djwong@us.ibm.com \
    --cc=hmh@hmh.eng.br \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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).