Comment 7 for bug 890337

Revision history for this message
Tuomas Heino (iheino+ub) wrote :

http://bazaar.launchpad.net/~vcs-imports/gnome-disk-utility/master/view/head:/src/gdu/gdu-linux-lvm2-volume-group.c?start_revid=930 has the following comment in find_pvs():

187 /* TODO: do incremental list management instead of recomputing on
188 * each add/remove/change event
189 */

So seems it is recomputing all LVM PVS's on every single change event. Raid resync likely generates a ton of those (resync status %). Do all of those change events get queued and then processed slowly, consuming change events at far lower rate than they are being generated?