On 21/12/20 2:35 pm, Emmanuel Dreyfus wrote:
On Mon, Dec 21, 2020 at 01:53:06PM +0530, Ravishankar N wrote:
Are you talking about the entries inside.glusterfs/indices/xattrop/* ? Any
stale entries here should automatically be purged when self-heal daemon as
it crawls the folder periodically.
On Mon, Dec 21, 2020 at 01:53:06PM +0530, Ravishankar N wrote:
> Are you talking about the entries inside.glusterfs/indices/xattrop/* ? Any
> stale entries here should automatically be purged when self-heal daemon as
> it crawls the folder periodically.
I mean for instance:
# ls -l
On 21/12/20 1:16 pm, Emmanuel Dreyfus wrote:
On a healthy system, one should definitely not remove any files or sub
directories inside .glusterfs as they contain important metadata. Which
entries specifically inside .glusterfs do you think are stale and why?
There are indexes leading to no
> On a healthy system, one should definitely not remove any files or sub
> directories inside .glusterfs as they contain important metadata. Which
> entries specifically inside .glusterfs do you think are stale and why?
There are indexes leading to no file, causing heal complains.
--
Emmanuel
On 21/12/20 7:10 am, Emmanuel Dreyfus wrote:
Hello
I have a lot of stale entries in bricks' .glusterfs directories. Is it
safe to just rm -rf it and hope for automatic rebuild? Reading the
source and experimenting, it does not seems obvious.
Or is there a way to clean up stale entries that
Hello
I have a lot of stale entries in bricks' .glusterfs directories. Is it
safe to just rm -rf it and hope for automatic rebuild? Reading the
source and experimenting, it does not seems obvious.
Or is there a way to clean up stale entries that lead to files that do
not exist anymore?
--
