Re: Weird hard disk noise on shutdown (bug #7674)

[Tejun Heo]

Rob Landley wrote:
>> Distros should update their shutdown(8) to do the followings.
>> Check whether /sys/modules/libata/parameters/spindown_compat exists. If it
>> does, write 0 to it. For each libata harddisk
>> Check whether /sys/class/scsi_disk/h:c:i:l/manage_start_stop exists. If it
>> doesn't, synchronize cache and spin the disk down as before. If it does, do
>> nothing and continue to the next disk. The file is also accessible as
>> /sys/block/sdX/device/scsi_disk:*/manage_start_stop.
> 
> You're saying all this is to work around kernels _before_ 2.6.22, and instead 
> of updating your shutdown you could just either update the kernel instead?

Yeap, I was assuming most shutdown(8)s were spinning down disks, which
apparently is wrong.  If shutdown(8) doesn't do that, you can just
upgrade the kernel and be done with it.  I'll submit update for the page
in a few hours.

>> If exists some, at this point, exotic shutdown(8) implementation that
>> is trying to issue STANDBYBOW on libata/scsi devices, it will get a
>> fat warning. The warning could also state that the only supported way
>> is to leave complete responsibility of spinning down the hard disks to
>> kernel, so eventually it could be cleaned of checks and compatibility
>> options.
> 
> I'm all for leaving this to the kernel.  I play in the embedded space a lot, 
> so the less I can get away with doing, the better. :)

Yeap, that's what's being done here.  For all SCSI disks (real SCSI,
SATA, USB, whatnot), it's now controlled by sysfs node
manage_start_stop.  Low level drivers can turn them on by default and
userland can change them by echoing to it.

-- 
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/