Thanks Nithya & Amar for the response.
Please let us know if you need more info from our side. We are looking into the source code of Glusterfs.
Regards,
Chandranana
Nithya Balachandran ---02/21/2019 08:46:02 AM---On Wed, 20 Feb 2019 at 21:03, Amar Tumballi Suryanarayan < atumball@xxxxxxxxxx> wrote:
From: Nithya Balachandran <nbalacha@xxxxxxxxxx>
To: Amar Tumballi Suryanarayan <atumball@xxxxxxxxxx>
Cc: Chandranana Naik <Chandranana.Naik@xxxxxxx>, Abhay Singh <abhays@xxxxxxxxxx>, Gluster Devel <gluster-devel@xxxxxxxxxxx>
Date: 02/21/2019 08:46 AM
Subject: Re: [Gluster-devel] GlusterFs v4.1.5: Need help on bitrot detection
On Wed, 20 Feb 2019 at 21:03, Amar Tumballi Suryanarayan <atumball@xxxxxxxxxx> wrote:
- Hi Chandranana,
We are trying to find a BigEndian platform to test this out at the moment, will get back to you on this.
Meantime, did you run the entire regression suit? Is it the only test failing? To run the entire regression suite, please run `run-tests.sh -c` from glusterfs source repo.
They are seeing other issues as well [1] , mostly related to the hashed values in Big endian systems and the hardcoded names and paths in the .t files. I have fixed 2 .t files and asked them to debug the remaining tests and provide patches as it was taking a long time to go back and forth with various suggested changes.
There are debug logs attached for all the failing tests, including one for the failing bitrot case which indicates a very large value being returned in fgetxattr (probably also related to endianess).
[2019-02-14 09:12:05.140750] D [MSGID: 0] [io-threads.c:372:iot_schedule] 0-patchy-io-threads: FGETXATTR scheduled as least priority fop
[2019-02-14 09:12:05.140828] A [MSGID: 0] [mem-pool.c:118:__gf_calloc] : no memory available for size (176093659239) [call stack follows]
/usr/local/lib/libglusterfs.so.0(+0x28eaa)[0x3ffb2da8eaa]
/usr/local/lib/libglusterfs.so.0(_gf_msg_nomem+0x31c)[0x3ffb2da93c4]
/usr/local/lib/libglusterfs.so.0(__gf_calloc+0x13c)[0x3ffb2dd595c]
/usr/local/lib/glusterfs/4.1.5/xlator/features/bitrot-stub.so(+0xe3c4)[0x3ffae28e3c4]
/usr/local/lib/glusterfs/4.1.5/xlator/storage/posix.so(+0x32154)[0x3ffae7b2154]
Regards,
Nithya
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1672480
- -Amar
On Tue, Feb 19, 2019 at 1:31 AM Chandranana Naik <Chandranana.Naik@xxxxxxx> wrote:
Hi Team,
We are working with Glusterfs v4.1.5 on big endian platform(Ubuntu 16.04) and encountered that the subtest 20 of test ./tests/bitrot/bug-1207627-bitrot-scrub-status.t is failing.
Subtest 20 is failing as below:
trusted.bit-rot.bad-file check_for_xattr trusted.bit-rot.bad-file //d/backends/patchy1/FILE1
not ok 20 Got "" instead of "trusted.bit-rot.bad-file", LINENUM:50
FAILED COMMAND: trusted.bit-rot.bad-file check_for_xattr trusted.bit-rot.bad-file //d/backends/patchy1/FILE1
The test is failing with error "remote operation failed [Cannot allocate memory]" logged in /var/log/glusterfs/scrub.log.
Could you please let us know if anything is missing in making this test pass, PFA the logs for the test case
(See attached file: bug-1207627-bitrot-scrub-status.7z)
Note: Enough memory is available on the system.
Regards,
Chandranana Naik
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel
--
Amar Tumballi (amarts)
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
