If we've found one bad disk, what are our options?
On Thu, Sep 30, 2010 at 10:12 AM, Richard Elling <richard.ell...@gmail.com>wrote: > On Sep 30, 2010, at 2:32 AM, Tuomas Leikola wrote: > > > On Thu, Sep 30, 2010 at 1:16 AM, Scott Meilicke < > scott.meili...@craneaerospace.com> wrote: > > Resliver speed has been beaten to death I know, but is there a way to > avoid this? For example, is more enterprisy hardware less susceptible to > reslivers? This box is used for development VMs, but there is no way I would > consider this for production with this kind of performance hit during a > resliver. > > > > > > According to > > > > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6494473 > > > > resilver should in later builds have some option to limit rebuild speed > in order to allow for more IO during reconstruction, but I havent't found > any guides on how to actually make use of this feature. Maybe someone can > shed some light on this? > > Simple. Resilver activity is throttled using a delay method. Nothing to > tune here. > > In general, if resilver or scrub make a system seem unresponsive, there is > a > root cause that is related to the I/O activity. To diagnose, I usually use > "iostat -zxCn 10" > (or similar) and look for unusual asvc_t from a busy disk. One bad disk > can ruin > performance for the whole pool. > -- richard > > -- > OpenStorage Summit, October 25-27, Palo Alto, CA > http://nexenta-summit2010.eventbrite.com > ZFS and performance consulting > http://www.RichardElling.com > > > > > > > > > > > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
