On Wed, Apr 11, 2012 at 03:34:32PM +1000, Tim Connors wrote:
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.
the issue is my LSI mp2sas controller card still being in RAID JBOD mode because I haven't been able to reflash it to IT mode in my current motherboard. This means it has drive seek & read timeouts tuned for enterprise drives in a data center that don't spin down except on explicit request, not consumer grade drives. anyway, the card times out and reports an error. ZFS sees the error and takes it at face value (as it should). as a i said, it's specific to my particular setup. it's probably fine on motherboard sata ports. and 'hdparm -S 0' did stop the problems so, from my POV - problem solved. also, fans. my hot swap bays have decent 120mm fans behind them, so i'm not too worried about them overheating even on 40+ degree days. i wouldn't expect any off-the-shelf mini-nas box to have decent cooling. that's one of the reasons i built my own. cost is the other major reason, i could build my own for a small fraction of the price of an OTS model and end up with a bigger, better, faster, more scalable system.
it. of much less importance, I also found that hddtemp woke the drives up anyway, whenever it queried the temperature.
I have never encountered that problem.
try idling a drive, then querying the temp with hddtemp or smartctl. It will spin it up. I haven't yet found a hard-disk brand that doesn't do this - so far tested seagate, western digital, hitachi, and samsung. craig -- craig sanders <cas@taz.net.au> BOFH excuse #350: paradigm shift...without a clutch