[Bugs] [Bug 1596686] key = trusted.glusterfs.protect.writes [Invalid argument]; key = glusterfs.avoid.overwrite [Invalid argument]

bugzilla at redhat.com bugzilla at redhat.com
Tue Jul 10 05:32:17 UTC 2018


https://bugzilla.redhat.com/show_bug.cgi?id=1596686

Nithya Balachandran <nbalacha at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nbalacha at redhat.com
              Flags|                            |needinfo?(kcao22003 at gmail.c
                   |                            |om)



--- Comment #5 from Nithya Balachandran <nbalacha at redhat.com> ---
(In reply to kcao22003 from comment #0)
> Description of problem:
> 
> We are currently using gluster version 4.0.0. We have three gluster server
> nodes
> and a gluster volume, MyVol with quota being enabled and a limit usage is
> set to a arbitrary number such as 1GB.
> 
> We see a lot of logging messages at INFO level in
> /var/log/glusterfs/bricks/mnt-[xxx]-[VOLUME_NAME].log:
> 
> [<TIMESTAMP1>] I [dict.c:491: dict_get] (
> -->/usr/lib64/glsuterfs/4.0.0/xlator/storage/posix.so(+0x25953)
> [0x7f73e0c62953] -->
> /usr/lib64/glusterfs/4.0.0/xlator/storage/posix.so(+0xc132) [0x7f73e0c49132]
> --> /lib64/libglusterfs.so.0(dict_get +0x10c) [0x7f73e836487c] 0-dict: !this
> || key = trusted.glusterfs.protect.writes [Invalid argument]
> 
> [<TIMESTAMP2>] I [dict.c:491: dict_get] (
> -->/usr/lib64/glsuterfs/4.0.0/xlator/storage/posix.so(+0xc1b7)
> [0x7f73e0c491b7] -->
> /usr/lib64/glusterfs/4.0.0/xlator/storage/posix.so(+0xc132) [0x7f73e0c49132]
> --> /lib64/libglusterfs.so.0(dict_get +0x10c) [0x7f73e836487c] 0-dict: !this
> || key = glusterfs.avoid.overwrite [Invalid argument]
> 
> 
> These two messages (with different HEX codes) are written to the same log
> file over and over and filled up the disk within a few days.
> 
> Does anyone know what is going on and any/or issue related to these
> messages? 
> 
> Thank you for your support.
> 

Were you running a rebalance when you saw these messages?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list