olifre posted a comment on ticket #3

This problem is caused by hd-idle watching /proc/diskstats, and if read / written blocks for the disk did not change after the last spindown was issued, it assumes the disk has not spun up. Since nothing is read / written during suspend / resume, this is a case not detected by hd-idle. The rewrite by adelolmo (also called hd-idle) uses two approaches to try to workaround this problem: - Send a spindown command anyways all three intervals. - Restart itself via the systemd service unit after each suspend....

Kurt Fitzner created ticket #4

Request: Incorporate libblkid for UUID support

Stephan created ticket #4

Debian Bullseye dependency problem

François Patte posted a comment on discussion Help

Bonjour, I have just installed hd-idle on a debian (10) based system. Here is what I wrote in /etc/default/hd-idle file: HD_IDLE_OPTS="-i 0 -a /dev/disk/by-uuid b3fdaa3a-8855-41e3-adab-a4147270ae62 -i 600 -l /var/log/hd-idle/hd-idle.log" I have a few questions: 1- The uuid is the one of a raid 1 array of two disks. Will hd-idle spin down the two disks at the same time after 10 mn of idle state? 2- Some directories of this array are mounted (by nfs) on other machines. Will hd-idle spin down the disks...

halsboss posted a comment on ticket #3

pls close

halsboss created ticket #3

last updated

John Little posted a comment on ticket #3

(I've been using hd-idle for a few years now, thank you.) I'm on Kubuntu, and hd-idle reached our repository at least since 19.10. However, it installs with options just "-h", and one must edit /etc/default/hd-idle to uncomment a more useful setting. I suggest a mention of this in the man page.

Arun G created ticket #3

hd-idle doesn't work after resuming from sleep.

Alex Mestiashvili posted a comment on ticket #3

Ok. The ready for upload package lives here: https://salsa.debian.org/debian/hd-idle Once the freeze [0] is over I'll upload it. Right now it makes no sense, as new packages are not accepted during freeze. Best regards, Alex [0] https://release.debian.org/buster/freeze_policy.html On Sat, Mar 16, 2019 at 9:40 PM Christian Mueller cjmueller@users.sourceforge.net wrote: Hi, I've actually tried to get it into Debian a few years ago but folks never got back to me. If you'd like to give it another try,...

Christina Mueller posted a comment on ticket #3

Hi, I've actually tried to get it into Debian a few years ago but folks never got back to me. If you'd like to give it another try, please be my guest. Thanks, --Christian On Mar 16, 2019, at 4:05 PM, Alex Mestiashvili antpu@users.sourceforge.net wrote: Hi, If you like to get the package into Debian, these are probably the starting points: https://mentors.debian.net https://mentors.debian.net/ https://wiki.debian.org/RFP https://wiki.debian.org/RFP If you don't have time for it, I'll have a look....

Alex Mestiashvili posted a comment on ticket #3

Hi, If you like to get the package into Debian, these are probably the starting points: https://mentors.debian.net https://wiki.debian.org/RFP If you don't have time for it, I'll have a look.

Matthew Murdock posted a comment on ticket #2

I created a patch to address the resume issue. The approach taken here is to identify if the sleep took longer than expected and reset the spum_down flag if we waited too long for the main loop sleep. This should capture suspend events as well as excessive machine load. I also added a few more log functions (included in the patch). Perhaps the logging could be revised as a separate thread, or employ syslog if your platform environment includes syslog?

Averell posted a comment on ticket #3

I would support the idea, but I don't know what can be done for that. Anyway, thanks for the software.

Christina Mueller posted a comment on ticket #3

Hi, I must admit I was hoping that it would eventually end up as a regular package in Debian (it believe it's in Fedora). Never happened, though.

Averell created ticket #3

deb file

Ernst K created ticket #2

fix for failure after system suspend/resume

Kocayine posted a comment on discussion Help

Is there a max value for a harddrive before it could cause trouble? I'm thinking...

hd-idle released /hd-idle-1.05.tgz