Hi Venky,
Thanks a lot for the info.
--
Andrea
----- Reply message -----
From: "Venky Shankar" <yknev.shankar@xxxxxxxxx>
To: "Andrea Tartaglia" <me@xxxxxxxxxxxxxxxxxxx>
Cc: "Gluster Devel" <gluster-devel@xxxxxxxxxxx>
Subject: [Gluster-devel] glusterfs 3.6.0beta3 fills up inodes
Date: Thu, Nov 13, 2014 2:28 AM
From: "Venky Shankar" <yknev.shankar@xxxxxxxxx>
To: "Andrea Tartaglia" <me@xxxxxxxxxxxxxxxxxxx>
Cc: "Gluster Devel" <gluster-devel@xxxxxxxxxxx>
Subject: [Gluster-devel] glusterfs 3.6.0beta3 fills up inodes
Date: Thu, Nov 13, 2014 2:28 AM
It's safe to purge everything under .processed. That what geo-rep had already replicated, so it's OK to delete it.
Also, consider purging these entries periodically as geo-rep doesn't purge them on it's own (at least for now).
Venky
On Thu, Nov 13, 2014 at 3:27 AM, Andrea Tartaglia <me@xxxxxxxxxxxxxxxxxxx> wrote:
Hi guys,
I've got a geo-rep setup which copies data across 3 DCs, it works fine, but I've just spotted that the both the master and slave server ( the main ones ) ran out of inodes.
Looking through the directories which have lots of files, the "/var/lib/misc/glusterfsd/[volname]/[connection]/.processed has got thousands of xsync changelog files
I'm using glusterfs 3.6.0beta3, as incurred in a bug while using 3.5.2 which was preventing geo-rep to work properly
Any idea if it's ok to delete what's in the processed directory at least as a temporary fix or if there's anything else I can do to prevent that happening other than increasing disk size?
Thanks
--
Andrea
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
