gmirror State: STALE

[R. B. Riddick]

--- Deomid Ryabkov <myself at rojer.pp.ru> wrote:
> Pawel Jakub Dawidek wrote:
> > 
> > BTW. Are you sure you don't want to use autosynchronization?
> > 
> 
> [...]
> I think, that ultimately should be handled in the base system:
> do not let mirror sync and fsck collide, ever.
> 
I experienced the same problem... Especially when there are two mirrors on the
same two disks... Somehow the head positioning times increase the overall
processing time much more than linear...

I think it would be a good idea to change the rebuild-strategy (maybe something
that is slower; e. g. one rebuild-request per 20 other requests or when there
are no pending other requests) in case of high load (e. g. fsck), although that
would increase the risk of data loss (another strategy could be, that other
requests are delayed until 20 rebuild-requests have been completed).

There is another problem in my setting: The rebuild of the other mirror devices
that use the same disk(s) should be delayed...

-Arne


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com