On Wed, 11 Apr 2012, Tim Connors wrote:
On Wed, 11 Apr 2012, Craig Sanders wrote:
On Wed, Apr 11, 2012 at 09:36:43AM +1000, Aníbal Monsalve Salazar wrote:
[ Cc-ing madduck as he may be interested on Craig's comments above ]
btw, i had already disabled idle spindown with hdparm -S 0
idle3-tools just updates the firmware settings so that it's disabled by default (as should be the recommend setting for WD Green drives on any linux system)..
I had experimented with spindown over summer (didn't want my drives to overheat) but found that ZFS didn't like it. at all. kept getting drives being booted from the zpool seemingly at random,
Er. How do we fix this? I was very much planning to implement zfsonlinux on my miniature NAS. That I want to keep operating in summer with good reliability despite my non-climate-controlled house. Mdadm and DM don't care about how long it takes to spin up a disk. This Is How It Should Be.
For fuck's sake. Responses on the web seem to be:
I am wondering whether it might not simply be a timeout issue, that is: the drive is taking too long to spin up, which causes a timeout and a read error to be reported, which then disappears completely once the drive has spun up.
The power management settings put your drive to sleep after some time of inactivity.
Unfortunately the only way I have found to adjust this is from a windows pc utility. (You can download it from their website)". No, the disk isn't taking too long to spin up. The timeout is too short. How do we convince the ZFS code to be slightly more reliable? Hopefully it's in the manpage. I haven't yet progressed as far as working out how to install zfsonlinux, but if this happens to be impossible to configure, then there's no point in me looking any further. I *know* that mdadm and ext4 already do the right thing (I was just hoping for something "better"). -- Tim Connors