Hello,
I am running GlusterFS 3.10.7 and just noticed by doing a "gluster volume quota
list" that my quotas on that volume are broken. The command returns
no output and no errors but by looking in /var/log/glusterfs.cli I found the
following errors:
[2018-02-09 19:31:24.242324] E
[cli-cmd-vo
On 09-Feb-2018 7:07 PM, "Seva Gluschenko" wrote:
Hi Karthik,
Thank you very much, you made me much more relaxed. Below is getfattr
output for a file from all the bricks:
root@gv2 ~ # getfattr -d -e hex -m . /data/glusterfs/testset/306/
30677af808ad578916f54783904e6342.pack
getfattr: Removing
Hi Karthik,
Thank you very much, you made me much more relaxed. Below is getfattr output
for a file from all the bricks:
root@gv2 ~ # getfattr -d -e hex -m .
/data/glusterfs/testset/306/30677af808ad578916f54783904e6342.pack
getfattr: Removing leading '/' from absolute path names
# file: data/glu
On Fri, Feb 9, 2018 at 3:23 PM, Seva Gluschenko wrote:
> Hi Karthik,
>
> Thank you for your reply. The heal is still undergoing, as the
> /var/log/glusterfs/glustershd.log keeps growing, and there's a lot of
> pending entries in the heal info.
>
> The gluster version is 3.10.9 and 3.10.10 (the ve
Hi Karthik,
Thank you for your reply. The heal is still undergoing, as the
/var/log/glusterfs/glustershd.log keeps growing, and there's a lot of pending
entries in the heal info.
The gluster version is 3.10.9 and 3.10.10 (the version update in progress). It
doesn't have info summary [yet?], an
+gluster-users
Another guideline we can provide is to disable all performance xlators for
workloads requiring strict metadata consistency (even for non gluster-block
usecases like native fuse mount etc). Note that we might still can have few
perf xlators turned on. But, that will require some e
