SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I hit this a couple of days ago - on a newly upgraded to current slackware 14 64 bit system.
In short - gvfsd-metadata gets confused, and thrashes the disk, creating and deleting files. https://bugzilla.gnome.org/show_bug.cgi?id=637095 seems relevant - and I think it's fixed in their tree.
I moved the dir in question onto a ramdisk - in the hopes that it was just a one-off and restarted the daemon - but something seemed to trigger it.
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
20.92 0.002901 0 189762 open
In 10 seconds
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Rep:
Hi SpeedEvil,
as far as I can see the bug you reffered to is relevant to your issue.
There are a few options for you to fix this.
1. Download the Slackbuild source file for gvfs, and include the patches that are reffered to in the bug report.
2. same as above but ask pat to include those fixes in -current
2. Ask/wait for pat to update gvfs to 1.18.x (this would also mean updating glib (hard dep) and some other libraries to the new stable series, that got released last week.)
3. Update yourself to gvfs 1.18.x and update the required dependencies aswell.
Dependecy list is as follows: (could miss a package)
glib-2.38.x
libarchive-3.x (without libarchive-3.x or option --disable-archive added to configure, your make will fail)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.