Re: clean up of unclean files

[Vijay Bellur <vbellur@xxxxxxxxxx>]

On Wed, Jun 13, 2018 at 3:39 PM, Brian Andrus <toomuchit@xxxxxxxxx> wrote:

All,

I have a 5x3 Distributed-Replicate filesystem that has a few entries that do not clean up when being healed.

I had tracked down what they were and since they were really just temp/expendable files, I moved the directory and recreated what was needed.

.glusterfs directory in the brick root contains metadata about the data stored in bricks. While the directory was moved, could it be possible that metadata in .glusterfs was not cleaned up?

 

Now those files in the recreated directory cannot be deleted and they show up in the gluster volume heal <volume> info output and never go away.

Examples below:

Brick brick5.internal:/GLUSTER/brick1
<gfid:8ed6a9e9-2820-40bd-8d9d-77b7f79c7748> - Is in split-brain

Status: Connected
Number of entries: 1

Brick brick6.internal:/GLUSTER/brick1
<gfid:8ed6a9e9-2820-40bd-8d9d-77b7f79c7748>/resv_state
<gfid:8ed6a9e9-2820-40bd-8d9d-77b7f79c7748> - Is in split-brain

<gfid:8ed6a9e9-2820-40bd-8d9d-77b7f79c7748>/node_state
<gfid:8ed6a9e9-2820-40bd-8d9d-77b7f79c7748>/job_state.old
<gfid:8ed6a9e9-2820-40bd-8d9d-77b7f79c7748>/node_state.old
Status: Connected
Number of entries: 5

So, how do I clean those up so they aren't showing up anywhere at all?

output of `heal <volname> info`  is derived by looking up metadata in .glusterfs and that metadata would need to be cleaned up, if stale, for the heal commands to function properly. You could move/unlink contents that correspond to stale data in .glusterfs/indices/xattrop directory under the brick root to have a clean state.

Regards,

Vijay

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users