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? ** Package changed: gvfs (Ubuntu) => gnome-disk-utility (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/890337 Title: gvfs-gdu-volume-monitor high cpu usage during raid-resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/890337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
