Skip to contentSkip to conversation

libata resume fix

PATCH Robert Hancock 4 participants 6 messages Jun 1, 2006 – Jun 6, 2006 5 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 5 lines · Bill Davidsen

The trade-off is that if I have a 15k rpm SCSI drive, it would take a lot of design changes to make it spin up quickly, and improve a function which is usually done on a server once every MTBF when replacing the failed unit.

I think the majority of very large or very fast drives are in systems which don't (deliberately) power cycles often, in rooms where heat is an issue. And to spin up quickly take a larger power supply... 30 sec is fine with most users.

Couldn't find a spin-up time for the new Seagate 750GB drive, but the seek sure is fast!

I wouldn't guess that even a 15K drive would take nearly that long. For boot time on servers it doesn't matter much though, disk spinup time is in the noise compared to the insane BIOS delays on most of them during bootup. Like on some servers (ahem.. IBM) which have about a 15 second delay on the main BIOS screen, 10 second delays on every network boot ROM, a 1 minute delay on the SCSI controller before it even starts scanning the bus, then another good 10 seconds before it starts booting. Gets annoying after a few reboots..

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
#6 lore raw
Quoted 11 lines · Robert Hancock
Quoted 10 lines · Bill Davidsen

The trade-off is that if I have a 15k rpm SCSI drive, it would take a lot of design changes to make it spin up quickly, and improve a function which is usually done on a server once every MTBF when replacing the failed unit.

I think the majority of very large or very fast drives are in systems which don't (deliberately) power cycles often, in rooms where heat is an issue. And to spin up quickly take a larger power supply... 30 sec is fine with most users.

Quoted 5 lines
Quoted 2 lines

Couldn't find a spin-up time for the new Seagate 750GB drive, but the seek sure is fast!

I wouldn't guess that even a 15K drive would take nearly that long. For boot time on servers it doesn't matter much though, disk spinup time is

I do use a 15K rpm drive in my workstation (hello git!), and the spin up really isn't that bad. Less than 10 seconds for the actual spin up, I would say.

Quoted 6 lines

in the noise compared to the insane BIOS delays on most of them during bootup. Like on some servers (ahem.. IBM) which have about a 15 second delay on the main BIOS screen, 10 second delays on every network boot ROM, a 1 minute delay on the SCSI controller before it even starts scanning the bus, then another good 10 seconds before it starts booting. Gets annoying after a few reboots..

Indeed, the BIOS bootup time on servers is typically anywhere from really bad to truly awful.

Signature · 1 line
Jens Axboe
#7 lore raw
Quoted 13 lines · Jens Axboe
Quoted 10 lines · Robert Hancock
Quoted 7 lines · Bill Davidsen

The trade-off is that if I have a 15k rpm SCSI drive, it would take a lot of design changes to make it spin up quickly, and improve a function which is usually done on a server once every MTBF when replacing the failed unit.

I think the majority of very large or very fast drives are in systems which don't (deliberately) power cycles often, in rooms where heat is an issue. And to spin up quickly take a larger power supply... 30 sec is fine with most users.

Couldn't find a spin-up time for the new Seagate 750GB drive, but the seek sure is fast!

Quoted 9 lines
Quoted 3 lines

I wouldn't guess that even a 15K drive would take nearly that long. For boot time on servers it doesn't matter much though, disk spinup time is

I do use a 15K rpm drive in my workstation (hello git!), and the spin up really isn't that bad. Less than 10 seconds for the actual spin up, I would say.

Sounds about right, but clearly longer than the 2 sec mentioned early in this thread. I think a long delay is okay as long as it gets stopped when the drive does come ready.

Quoted 11 lines
Quoted 5 lines

in the noise compared to the insane BIOS delays on most of them during bootup. Like on some servers (ahem.. IBM) which have about a 15 second delay on the main BIOS screen, 10 second delays on every network boot ROM, a 1 minute delay on the SCSI controller before it even starts scanning the bus, then another good 10 seconds before it starts booting. Gets annoying after a few reboots..

Indeed, the BIOS bootup time on servers is typically anywhere from really bad to truly awful.

I try *very* hard not to do bootup on servers, the paperwork involved with an outage takes longer than the boot time ;-)

Signature · 3 lines
bill davidsen <[email protected]>
 CTO TMR Associates, Inc
 Doing interesting things with small computers since 1979
#8 lore raw
In reply to Jens Axboe

Hi, Jens.

Quoted 4 lines · Jens Axboe
Quoted 3 lines · Robert Hancock
Quoted 2 lines · Bill Davidsen

The trade-off is that if I have a 15k rpm SCSI drive, it would take a lot of design changes to make it spin up quickly, and improve a function which is usually done on a server once every MTBF when replacing the failed unit.

Quoted 8 lines
Quoted 4 lines
Quoted 3 lines

I think the majority of very large or very fast drives are in systems which don't (deliberately) power cycles often, in rooms where heat is an issue. And to spin up quickly take a larger power supply... 30 sec is fine with most users.

Couldn't find a spin-up time for the new Seagate 750GB drive, but the seek sure is fast!

I wouldn't guess that even a 15K drive would take nearly that long. For boot time on servers it doesn't matter much though, disk spinup time is

I do use a 15K rpm drive in my workstation (hello git!), and the spin up really isn't that bad. Less than 10 seconds for the actual spin up, I would say.

Can you measure spin up time for your 15k's? Some controllers can't catch the first D2H FIS after POR and have to wait unconditionally for spin up for hotplug & resuming from suspend. Currently 8 sec wait is used but it seems insufficient for your drives. Failing to spinup in that 8 secs would probably result in timeout of the first reset attempt and retrial - which currently takes > 30 secs.

Spin-up time can be measured by first issuing STANDBY and then time how long IDLE IMMEDIATE takes, I think.

Thanks.

Signature · 1 line
tejun
#9 lore raw
Quoted 31 lines · Tejun Heo

Hi, Jens.

Quoted 12 lines · Jens Axboe
Quoted 11 lines · Robert Hancock
Quoted 10 lines · Bill Davidsen

The trade-off is that if I have a 15k rpm SCSI drive, it would take a lot of design changes to make it spin up quickly, and improve a function which is usually done on a server once every MTBF when replacing the failed unit.

I think the majority of very large or very fast drives are in systems which don't (deliberately) power cycles often, in rooms where heat is an issue. And to spin up quickly take a larger power supply... 30 sec is fine with most users.

Quoted 8 lines
Quoted 4 lines
Quoted 2 lines

Couldn't find a spin-up time for the new Seagate 750GB drive, but the seek sure is fast!

I wouldn't guess that even a 15K drive would take nearly that long. For boot time on servers it doesn't matter much though, disk spinup time is

I do use a 15K rpm drive in my workstation (hello git!), and the spin up really isn't that bad. Less than 10 seconds for the actual spin up, I would say.

Can you measure spin up time for your 15k's? Some controllers can't catch the first D2H FIS after POR and have to wait unconditionally for spin up for hotplug & resuming from suspend. Currently 8 sec wait is used but it seems insufficient for your drives. Failing to spinup in that 8 secs would probably result in timeout of the first reset attempt and retrial - which currently takes > 30 secs.

Quoted 2 lines

Spin-up time can be measured by first issuing STANDBY and then time how long IDLE IMMEDIATE takes, I think.

The 15K RPM is a SCSI drive, I haven't seen any SATA 15K rpm drives yet. I have the same model in another box, I can measure spinup with START_STOP unit there. I will do so later today, when I fire it up, if you still want to know?

Signature · 1 line
Jens Axboe
#10 lore raw
Quoted 9 lines · Jens Axboe
Quoted 3 lines

Can you measure spin up time for your 15k's? Some controllers can't catch the first D2H FIS after POR and have to wait unconditionally for spin up for hotplug & resuming from suspend. Currently 8 sec wait is used but it seems insufficient for your drives. Failing to spinup in that 8 secs would probably result in timeout of the first reset attempt and retrial - which currently takes > 30 secs.

Spin-up time can be measured by first issuing STANDBY and then time how long IDLE IMMEDIATE takes, I think.

The 15K RPM is a SCSI drive, I haven't seen any SATA 15K rpm drives yet. I have the same model in another box, I can measure spinup with START_STOP unit there. I will do so later today, when I fire it up, if you still want to know?

Arggh.. Confused w/ 10k drives. But it would be nice to know spin-up time for 15k's if it doesn't waste too much of your time.

Thanks.

Signature · 1 line
tejun