[Gluster-users] Deleted file sometimes remains in .glusterfs/unlink
spisla80 at gmail.com
Tue Nov 20 10:03:57 UTC 2018
I am using Gluster v4.1.5. I have replica 4 volume. This is the info:
Volume Name: testv1
Volume ID: a5b2d650-4e93-4334-94bb-3105acb112d1
Snapshot Count: 0
Number of Bricks: 1 x 4 = 4
Am Di., 20. Nov. 2018 um 07:33 Uhr schrieb Ravishankar N <
ravishankar at redhat.com>:
> On 11/19/2018 08:18 PM, David Spisla wrote:
> Hello Gluster Community,
> sometimes it happens that a file accessed via FUSE or SMB will remain in
> .glusterfs/unlink after delete it. The command 'df -hT' still prints the
> volume capacity before the files was deleted. Another observation is that
> after waiting a hole nigth the file is removed completely and there is the
> correct capacit . Is this behaviour "works as design"?
> Is this a replicate volume? Files end up in .glusterfs/unlink post
> deletion only if there is still an fd open on the file. Perhaps there was
> an on going data-self heal or another application had not yet closed the
> file descriptor?
> Which version of gluster are you using and what is the volume info?
> The issue was mentioned here already:
> and there seems to be a fix . But unfortunately it still occurs and there
> is only the workaround to restart the brick processes or wait for some
> David Spisla
> Gluster-users mailing listGluster-users at gluster.orghttps://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users