Re: [Gluster-users] Deleted file sometimes remains in .glusterfs/unlink

2018-11-19 Thread Ravishankar N
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

Re: [Gluster-users] Gluster 3.12.14: wrong quota in Distributed Dispersed Volume

2018-11-19 Thread Hari Gowtham
Hi, Can you check if the quota crawl finished? Without it having finished the quota list will show incorrect values. Looking at the under accounting, it looks like the crawl is not yet finished ( it does take a lot of time as it has to crawl the whole filesystem). If the crawl has finished and

[Gluster-users] Gluster 3.12.14: wrong quota in Distributed Dispersed Volume

2018-11-19 Thread Frank Ruehlemann
Hi, we're running a Distributed Dispersed volume with Gluster 3.12.14 at Debian 9.6 (Stretch). We migrated our data (>300TB) from a pure Distributed volume into this Dispersed volume with cp, followed by multiple rsyncs. After the migration was successful we enabled quotas again with "gluster

[Gluster-users] Deleted file sometimes remains in .glusterfs/unlink

2018-11-19 Thread David Spisla
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