Re: Dirty Parity

you could always change your raid scrub duration option to -1. this way it will run to completion.

On 3/7/07, Carl Howell chowell@uwf.edu wrote:

*This is my second attempt to send this to the list. If it shows up twice, I apologize.

We had a situation last year in which one of the aggregates on our R100 suffered dirty parity in one of its raid groups which forced us to take the filer down for several hours while we ran WAFL_Check on that aggregate. Given this, I have a few questions:

1.   What is the likelihood of getting dirty parity? I assume the
   

likelihood goes up dramatically on a box like the R100 given that the weekly RAID scrubs seldom if ever complete.

2.   If this had occurred on a cluster, could we take one node down to
   

run the WAFL_Check, while the other node continues to serve data from the other aggregates?

3.   How many of you have encountered something like this and decided to
   

go with SyncMirror to protect against such a thing?

Thanks,

--Carl