dick hoogendijk wrote:> Can I do a zpool scrub on a running server without effecting
> webserving / email serving? I read it is a I/O-intensive operation.
> Does that mean the server has to be idle? Or better still: go into
> maintenance (init S)? I guess not, but still..
>
It used to have a really bad effect on the performance of my Nevada
system (builds back in the 70''s), but more recently, I don''t
notice it
much (and I think it''s taking longer). I don''t know if someone
has done
something to reduce the load it places on the system, or maybe it''s
something to do with switching to the nv_sata driver, but whatever, the
impact is much less in current Nevada builds.
Don''t need to drop into single user or shut down the app. I would start
it at the beginning of a quiet period though, and monitor the system
performance, at least the first time you run it. You can cancel it if
you start seeing bad performance.
Note there was a bug whereby issuing the zpool status command as a
privileged user caused the scrub to restart (so if you kept looking, it
never appeared to be getting anywhere). It''s fixed now in Nevada
(don''t
know about in S10). Safest thing if you aren''t sure is to make sure you
issue zpool status command only as a non-priv user, which didn''t cause
a
scrub restart.
--
Andrew