https://bugzilla.redhat.com/show_bug.cgi?id=1672480
Raghavendra Bhat <rabhat at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rabhat at redhat.com
Flags| |needinfo?(abhaysingh1722 at ya
| |hoo.in)
--- Comment #47 from Raghavendra Bhat <rabhat at redhat.com> ---
I am looking at the bitrot error. The error is while doing a getxattr on the
xattr "trusted.glusterfs.get-signature". But one of the attached files
(bug-1207627-bitrot-scrub-status.log.txt) shows
the following extended attributes. Unfortunately "trusted.bit-rot.signature" is
not seen.
TEST 22 (line 55): trusted.bit-rot.bad-file check_for_xattr
trusted.bit-rot.bad-file //d/backends/patchy1/FILE1
not ok 22 Got "" instead of "trusted.bit-rot.bad-file", LINENUM:55
RESULT 22: 1
getfattr: Removing leading '/' from absolute path names
# file: d/backends/patchy1
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x000000010000000000000000ffffffff
trusted.glusterfs.volume-id=0xdc6b47ebd73f46798f5a86b42678fb44
Would it be possible for you to upload the bitd.log from /var/log/glusterfs
directory after running the bitrot test?
Because, it is bit-rot daemon (whose log file is bitd.log that I asked) which
sets sends the setxattr requests to the brick to set the extended attributes
needed for bit-rot detection.
If setting that attribute failed, then bit-rot daemon's log file would have got
an error.
Regards,
Raghavendra
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.