We all know that data corruption may happen, even on the most reliable
of hardware. That's why zfs har pool scrubbing.
Could we introduce a zpool option (as in zpool set <optionname> <pool>)
for "scrub period", in "number of hours" (with 0 being no automatic
scrubbing).
I see several modern raidcontrollers (such as the LSI Megaraid MFI line)
has such features (called "patrol reads") already built into them. Why
should zfs have the same? Having the zpool automagically handling this
(probably a good thing to default it on 168 hours or one week) would
also mean that the scrubbing feature is independent from cron, and since
scrub already has lower priority than ... actual work, it really
shouldn't annoy anybody (except those having their server under their bed).
Of course I'm more than willing to stand corrected if someone can tell
me where this is already implemented, or why it's not needed. Proper
flames over this should start with a "warning, flame" header, so I can
don my asbestos longjohns. ;)
//Svein
--
Sending mail from a temporary set up workstation, as my primary W500 is
off for service. PGP not installed.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
