tags 426224 upstream help confirmed
thanks
The proper fix to this bug requires:
1. That sysvinit hddown.c be fixed (and fixes sent upstream) so that:
a) it uses sysfs and not /proc to locate disks, and that it locates
all IDE and SCSI/libata disks, or maybe do both /proc and sysfs.
b) that it verifies the state of kernel disk spindown control for
each disk, and for the disks where it is unavailable:
b1) issue cache sync to disk
b2) issue spin down to disk
c) for the disks where kernel spin down control is available, enable
it and skip to next disk.
This is also likely to fix #178968, and it will also stop damaging expensive
SCSI disks on servers that are stand-alone and not part of a
multi-SCSI-initiator scenario. People with multi-initiator setups need to
configure the kernel properly, and sysvinit will by default leave their
disks alone (since the initscript will not call halt -h).
When the above is done, Debian should kill most of the abomination that is
the 67_init_hddown.patch patch.
Unfortunately, it is way too much for me to do and test right now, so I am
tagging it help. I hope one of the other sysvinit maintainers, or even
Miquels (sysvinit upstream) himself has the time to fix this properly.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
_______________________________________________
Pkg-sysvinit-devel mailing list
Pkg-sysvinit-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
