Bug 288084

Summary: dolphin locks up for several seconds during hdd spinup
Product: [Frameworks and Libraries] solid Reporter: Johannes E. Krause <j.k>
Component: libsolidAssignee: Alex Fiestas <afiestas>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugs.kde.org3
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description Johannes E. Krause 2011-12-02 20:35:47 UTC 
Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

i have configured my harddrives to spin down after being idle for 30 minutes. whenever the drive spins up due to activity, dolphin gets blocked.

Reproducible: Always

Steps to Reproduce:
1) hdparm -Y /dev/sda (halts drive immediately)
1a) hdparm -S 120 /dev/sda (spins the drive down after 30 minutes)
2) do something in dolphin, like open a subdirectory.

Actual Results:  
now, whenever the HDD is forced to spin up due to new activity, dolphin completely freezes until the spinup is complete. this is <<very annoying>>, because it will cancel drag&drop operations and similar, in general it totally interrupts whatever i was doing right now.

Expected Results:  

there should be a more graceful method to await the response of an IO operation.


on a related note:
when having symlinks that reach to another drive in a directory, that other drive will spin up just when opening the directory. there should be more aggressive caching methods to avoid that from happening.
Comment 1 hyper_ch 2011-12-03 06:37:22 UTC 
I suffer from this as well. I talked in IRC with Johannes yesterday and upon his suggestion I did alter the hdparms to -S 255 on my netbook:

"sudo hdparm -S 255 /dev/sda

/dev/sda:
 setting standby to 255 (21 minutes + 15 seconds)"

This has improved the behaviour a bit.


Currently I'm running:

Dolphin
Version 1.7
Using KDE Development Platform 4.7.3 (4.7.3)
Comment 2 Alex Fiestas 2013-03-02 00:11:11 UTC 
Mostly this happens because we lack an async api, going to be fixed in libsolid2

*** This bug has been marked as a duplicate of bug 253654 ***