Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I know there are related issues, but none of them seem to apply to my case. Below is iotop output. jbd2 is constantly above 90% usage. It's been grinding away for 2 days. It stops for a while after a reboot, but then starts again after some time. I'm using 32bit Ubuntu 13.04. 200GB WD disk. Smart disabled in bios. No raid configs.

 Total DISK READ:       0.00 B/s | Total DISK WRITE:    1997.25 K/s
  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND                                                             
  307 be/3 root        0.00 B/s  811.58 B/s  0.00 % 93.68 % [jbd2/sda1-8]
15454 be/4 curvv       0.00 B/s 1623.16 B/s  0.00 %  0.88 % firefox
 4305 be/4 curvv       0.00 B/s  721.23 K/s  0.00 %  0.70 % gvfsd-metadata
 2048 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % console-kit-daemon --no-daemon
    1 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % init
    2 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [kthreadd]
    3 be/4 root        0.00 B/s    0.00 B/s  0.00 %  0.00 % [ksoftirqd/0]
    ...
share|improve this question

closed as off-topic by Luis Alvarado Jul 25 at 1:51

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This describes a problem that can't be reproduced that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Luis Alvarado
If this question can be reworded to fit the rules in the help center, please edit the question.

2  
So this started again, grinding, grinding. I noticed gvfsd-metadata, pkilled it and jbd2 process went back to 0.00% usage and grinding stopped immediately. Trying to figure out what it actually does. From gvfsd-metadata man page: gvfsd-metadata is a daemon acting as a write serialiser to the internal gvfs metadata storage. It is autostarted by GIO clients when they make metadata changes. Read operations are done by client-side GIO code directly, and don't require the daemon to be running. The gvfs metadata capabilities are used by the nautilus file manager, for example. –  Curvian Vynes Jun 26 '13 at 18:41
    
unix.stackexchange.com/questions/108254/… has the same solution. I'm using kde, but nautilus started the other day, and left my disk spinning. This fixed the problem –  naught101 Apr 8 at 4:10

1 Answer 1

up vote 0 down vote accepted

I also ran the following commands to kill the process and remove the stored metadata.

pkill gvfsd-metadata 
rm -rf .local/share/gvfs-metadata
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.