After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 750113 - Corrupted metadata cache not fixed/removed
Corrupted metadata cache not fixed/removed
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: metadata
1.24.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2015-05-29 17:14 UTC by Gergely POLONKAI
Modified: 2018-09-21 17:49 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
metadata: Backup tree if meta_tree_init failed (3.03 KB, patch)
2015-06-05 12:01 UTC, Ondrej Holy 		none Details | Review

Description Gergely POLONKAI 2015-05-29 17:14:43 UTC 
I found this issue by setting my ~/Downloads folder’s ordering preferences. As it failed to get saved and asked around on #gnome I was told to try gvfs-info ~/Downloads | grep nautilus. The output was empty as of stdout, but a warning was printed on the screen:

(gvfs-info:19215): GVFS-WARNING **: can't init metadata tree /home/polesz/.local/share/gvfs-metadata/home: wrong size

The file was indeed 0 bytes long; removing it made gvfs to recreate it with the correct headers, and thus the nautilus ordering preferences could be saved. I suspect a filled hard drive caused the corruption back few months ago.
Comment 1 Ondrej Holy 2015-06-05 12:00:47 UTC 
Thanks for your bug report.

Maybe we should to apply same logic as in commit f7f18bb (Bug 598561). Backup the tree file in meta_tree_open if meta_tree_init fails...
Comment 2 Ondrej Holy 2015-06-05 12:01:36 UTC 
Created attachment 304642 [details] [review]
metadata: Backup tree if meta_tree_init failed

Alex, what do you think?
Comment 3 GNOME Infrastructure Team 2018-09-21 17:49:21 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/255.