With write-intent bitmaps our arrays, if dirty, are now reconstructed before anyone logs in. That avoided the conflict with 'zeitgeist'.
The fast recovery speed also suited our other requirements better, despite the trade-offs involved. Synchronization on this production system takes several hours. Unfortunately I am not in a position to trigger reconstruction at this time. If no one else reports a similar problem, please feel free to ignore this filing. -- You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. https://bugs.launchpad.net/bugs/889139 Title: zeitgeist-daemon degrades mdraid recovery Status in Zeitgeist Framework: Incomplete Bug description: Upon login, the 'zeitgeist-daemon' interferes with md raid recovery. Changing process priorities has no effect. Array reconstruction only takes place at a reasonable speed after one issues 'kill -STOP $zeitgeist-daemon-pid', followed by a 'kill -CONT $pid' when done. In my case reconstruction speed degrades to 1MB/s, which takes 4 days on a 320GB disk, from 50MB/s or 100 minutes with 'zeitgeist-daemon' suspended. Given that there is no protection from drive failure during reconstruction that task should be given priority. To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/889139/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
