I sprinkled some debug output into job-ata-smart-collect.c and it seems that the sk_disk_open() call spins up the disk even before the sleep mode gets checked.
sk_disk_open() is provided by libatasmart4, so should this bug be assigned there?
Strangely, hdparm -C manages to retrieve the sleep state correctly without spinning the disk up. Hdparm doesn't use libatasmart4, so it must use a more advanced method for getting smart data from a drive.
I sprinkled some debug output into job-ata- smart-collect. c and it seems that the sk_disk_open() call spins up the disk even before the sleep mode gets checked.
sk_disk_open() is provided by libatasmart4, so should this bug be assigned there?
Strangely, hdparm -C manages to retrieve the sleep state correctly without spinning the disk up. Hdparm doesn't use libatasmart4, so it must use a more advanced method for getting smart data from a drive.