Description: I spin down my hard drives with `hdparm` when they are not in use. I have an SDD and two internal harddrives (call them HDD1 and HDD2). The SDD contains the root filesystem and the trash location. When I put a file on the SDD into the Wastebin it spins up HDD1 (HDD2 stays idle). Steps to reproduce: 0. Prerequisite: A hard drive (I'll call it "HDD1") that is not the system drive. 1. Spin down HDD1: `hdparm -y /dev/sdb`. You can check with `hdparm -C /dev/sdb` if it has spun down, the output should be "standby". 2. On the system drive select a file, press key "Delete" and click on the "Wastebin" button. 3. Check whether HDD1 has spun backup with `hdparm -C /dev/sdb`. It should say "active/idle". PS: I love this file manager, been using it for years now. Your work is much appreciated!
Please test this with Dolphin. Same behaviour?
Alex, I just did some investigating and it turns out the problem is not as reproducible as I thought. Here is what I found out: 1. If I reboot, then spin down, then open Krusader (I make it start with both panes at $HOME) it spins up one or all hard drives even when I moved all symlinks in $HOME that pointed to the hard drives. In the same scenario Dolphin spins up all hard drives. If after this I spin down the hard drives and open either Krusader or Dolphin, they don't spin up anything anymore. 2. I can't easily reproduce the problem by moving to Wastebin. It seems if I recentely spun them down, moving to Wastebin doesn't spin them up (I'm guessing I must wait a while, because this problem has been happening to me for months now). I will try to run Krusader with `strace -e trace=open,close,read,write,connect,accept krusader` and see what file/dir it reads when moving to Wastebin spins disks up. I'll also try to leave Dolphin running for a while after spinning disks down, to see if moving to Wastebin in Dolphin also causes the problem.
@Alex I can confirm that it happens with Dolphin as well. I left Dolphin open for a few hours, then deleting to Wastebin spun up an unrelated drive.
It's possible that the trash directories on the hard drives are read. Or filesystem information (free space, etc.), hard to say.
The fact that you don't know, does this mean that the bug is outside of Krusader? That it's in a KDE component? If it is, could you provide some details and where is more appropriate to file this bug?
The problem is, I really don't know. Somebody has to further test this with inotify-tools or strace to make sure what/why something is read. Its probably not a bug in Krusader but I don't want to pass on bug reports to somebody else if its not really clear what actually is happening.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!