Skip to contentSkip to conversation

Reminder for feature libata spindown skipping and warning removal date Dec 2008

DISCUSSION Jaswinder Singh Rajput 2 participants 2 messages Jul 3, 2009

lore
Share & tools
lore
#0 lore raw

Hello Tejun,

What: libata spindown skipping and warning
When: Dec 2008
Why:  Some halt(8) implementations synchronize caches for and spin

down libata disks because libata didn't use to spin down disk on system halt (only synchronized caches).
Spin down on system halt is now implemented. sysfs node /sys/class/scsi_disk/h:c:i:l/manage_start_stop is present if spin down support is available.
Because issuing spin down command to an already spun down disk makes some disks spin up just to spin down again, libata tracks device spindown status to skip the extra spindown command and warn about it.
This is to give userspace tools the time to get updated and will be removed after userspace is reasonably updated.
Who: Tejun Heo <[email protected]>

If you are facing any issue regarding feature removal kindly update the "Documentation/feature-removal-schedule.txt" like what you are waiting for.

Thanks,
--
JSR

http://userweb.kernel.org/~jaswinder/

#1 lore raw
Quoted 18 lines · Jaswinder Singh Rajput

Hello Tejun,

What: libata spindown skipping and warning
When: Dec 2008
Why:  Some halt(8) implementations synchronize caches for and spin

down libata disks because libata didn't use to spin down disk on system halt (only synchronized caches).
Spin down on system halt is now implemented. sysfs node /sys/class/scsi_disk/h:c:i:l/manage_start_stop is present if spin down support is available.
Because issuing spin down command to an already spun down disk makes some disks spin up just to spin down again, libata tracks device spindown status to skip the extra spindown command and warn about it.
This is to give userspace tools the time to get updated and will be removed after userspace is reasonably updated.
Who: Tejun Heo <[email protected]>

Quoted 3 lines

If you are facing any issue regarding feature removal kindly update the "Documentation/feature-removal-schedule.txt" like what you are waiting for.

Thanks for the reminder. Just sent out patch to kill the feature. :-)

Signature · 1 line
tejun