[Desktop-packages] [Bug 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync

2016-02-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-disk-utility (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/890337

Title:
  gvfs-gdu-volume-monitor high cpu usage during raid-resync

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  During a raid-resync cpu usage is high - in fact gvfs-gdu-volume-
  monitor was using 100% cpu on one core for the duration of resync.
  Killed it with -SEGV to get something that can be retraced.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gvfs 1.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Nov 13 23:36:38 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_IE:en
   LANG=en_IE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e
   PC (0x7fca9329a3c3) ok
   source "0x7fca9329a32e" (0x7fca9329a32e) ok
   SP (0x7fff9b1adac0) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libgdu.so.0
   ?? () from /usr/lib/libgdu.so.0
  Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/890337/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync

2013-05-01 Thread Tuomas Heino
** Tags added: precise

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/890337

Title:
  gvfs-gdu-volume-monitor high cpu usage during raid-resync

Status in “gnome-disk-utility” package in Ubuntu:
  New

Bug description:
  During a raid-resync cpu usage is high - in fact gvfs-gdu-volume-
  monitor was using 100% cpu on one core for the duration of resync.
  Killed it with -SEGV to get something that can be retraced.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gvfs 1.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Nov 13 23:36:38 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_IE:en
   LANG=en_IE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e
   PC (0x7fca9329a3c3) ok
   source 0x7fca9329a32e (0x7fca9329a32e) ok
   SP (0x7fff9b1adac0) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libgdu.so.0
   ?? () from /usr/lib/libgdu.so.0
  Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/890337/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync

2011-11-26 Thread Tuomas Heino
** Attachment added: cpu usage does not drop after several hours of raid 
resync, uses a lot of memory too
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/890337/+attachment/2609183/+files/after_resync_status.txt

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/890337

Title:
  gvfs-gdu-volume-monitor high cpu usage during raid-resync

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  During a raid-resync cpu usage is high - in fact gvfs-gdu-volume-
  monitor was using 100% cpu on one core for the duration of resync.
  Killed it with -SEGV to get something that can be retraced.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gvfs 1.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Nov 13 23:36:38 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_IE:en
   LANG=en_IE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e
   PC (0x7fca9329a3c3) ok
   source 0x7fca9329a32e (0x7fca9329a32e) ok
   SP (0x7fff9b1adac0) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libgdu.so.0
   ?? () from /usr/lib/libgdu.so.0
  Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/890337/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync

2011-11-26 Thread Tuomas Heino
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 Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/890337

Title:
  gvfs-gdu-volume-monitor high cpu usage during raid-resync

Status in “gnome-disk-utility” package in Ubuntu:
  New

Bug description:
  During a raid-resync cpu usage is high - in fact gvfs-gdu-volume-
  monitor was using 100% cpu on one core for the duration of resync.
  Killed it with -SEGV to get something that can be retraced.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gvfs 1.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Nov 13 23:36:38 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_IE:en
   LANG=en_IE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e
   PC (0x7fca9329a3c3) ok
   source 0x7fca9329a32e (0x7fca9329a32e) ok
   SP (0x7fff9b1adac0) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libgdu.so.0
   ?? () from /usr/lib/libgdu.so.0
  Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/890337/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp