[Gluster-devel] Gluster Test Framwork tests failed on Gluster+Zfs(Zfs on linux)
Kiran Patil
kirantpatil at gmail.com
Thu Sep 4 10:59:26 UTC 2014
Hi Santosh,
May be if you or anyone could lay a way to add Zfs(ZOL) or Btrfs specific
test cases, that would be great and we could contribute our best to add new
test cases.
Thanks,
Kiran.
On Thu, Sep 4, 2014 at 4:19 PM, Santosh Pradhan <spradhan at redhat.com> wrote:
> Hi,
> Currently GlusterFS is tightly coupled with ext(2/3/4) and XFS. Zfs (ZOL)
> and Btrfs are not supported at the moment, may get supported in future (at
> least btrfs).
>
> Thanks,
> Santosh
>
>
>
> On 09/04/2014 03:34 PM, Justin Clift wrote:
>
>> On 28/08/2014, at 9:30 AM, Kiran Patil wrote:
>>
>>> Hi Gluster Devs,
>>>
>>> I ran the Gluster Test Framework on Gluster+zfs stack and found issues.
>>>
>>> I would like to know if I need to submit a bug at Redhat Bugzilla since
>>> the stack has zfs, which is not supported by Redhat or Fedora if I am not
>>> wrong?
>>>
>> Definitely create an issue on the Red Hat Bugzilla, for the "GlusterFS"
>> "product" ;> there:
>>
>> https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS
>>
>> Since it's for the upstream Community, the official Red Hat "Supported"
>> list isn't super relevant.
>>
>>
>> <snip>
>>
>>> Test Summary Report
>>> -------------------
>>> ./tests/basic/quota.t (Wstat: 0 Tests: 45
>>> Failed: 3) --> quota issue
>>> Failed tests: 24, 28, 32
>>> ./tests/bugs/bug-1004744.t (Wstat: 0 Tests: 14
>>> Failed: 4) --> passes on changing EXPECT_WITHIN 20 to EXPECT_WITHIN 30
>>> Failed tests: 10, 12-14
>>> ./tests/bugs/bug-1023974.t (Wstat: 0 Tests: 15
>>> Failed: 1) --> quota issue
>>> Failed test: 12
>>> ./tests/bugs/bug-824753.t (Wstat: 0 Tests: 16
>>> Failed: 1) --> file-locker issue
>>> Failed test: 11
>>> ./tests/bugs/bug-856455.t (Wstat: 0 Tests: 8
>>> Failed: 1) --> brick directory name is hardcoded while executing kill
>>> command
>>> Failed test: 8
>>> ./tests/bugs/bug-860663.t (Wstat: 0 Tests: 10
>>> Failed: 1) --> brick directory name is hardcoded and failed at TEST ! touch
>>> $M0/files{1..10000};
>>> Failed test: 8
>>> ./tests/bugs/bug-861542.t (Wstat: 0 Tests: 13
>>> Failed: 4) --> brick directory name is hardcoded and all EXPECT tests are
>>> failing
>>> Failed tests: 10-13
>>> ./tests/bugs/bug-902610.t (Wstat: 0 Tests: 8
>>> Failed: 1) --> brick directory name is hardcoded and EXPECT test failing
>>> Failed test: 8
>>> ./tests/bugs/bug-948729/bug-948729-force.t (Wstat: 0 Tests: 35
>>> Failed: 4) --> XFS related and brick directory name is hardcoded
>>> Failed tests: 15, 17, 19, 21
>>> ./tests/bugs/bug-948729/bug-948729-mode-script.t (Wstat: 0 Tests: 35
>>> Failed: 8) --> XFS related and brick directory name is hardcoded
>>> Failed tests: 15, 17, 19, 21, 24-27
>>> ./tests/bugs/bug-948729/bug-948729.t (Wstat: 0 Tests: 23
>>> Failed: 3) --> XFS related and brick directory name is hardcoded
>>> Failed tests: 12, 15, 23
>>> ./tests/bugs/bug-963541.t (Wstat: 0 Tests: 13
>>> Failed: 3) --> remove-brick issue
>>> Failed tests: 8-9, 13
>>> ./tests/features/glupy.t (Wstat: 0 Tests: 6
>>> Failed: 2)
>>> Failed tests: 2, 6
>>>
>>> Subset of the above bugs which can be reproduced on Glusterfs + ext4 is
>>> filed at Redhat bugzilla which is Bug id 1132496.
>>>
>> The glupy.t one I'll be able to look at, but not in the next few days. I
>> need
>> to finish my current task, and then to get my head back into Glupy.
>>
>> bug-1004744.t and the tests with hard coded brick directory names may be
>> easy
>> to fix. The others I'm not sure about.
>>
>> Do you have any interest in creating the fixes for the one's you're
>> comfortable with, and submitting them through Gerrit? (review.gluster.org
>> )
>>
>> Regards and best wishes,
>>
>> Justin Clift
>>
>> --
>> GlusterFS - http://www.gluster.org
>>
>> An open source, distributed file system scaling to several
>> petabytes, and handling thousands of clients.
>>
>> My personal twitter: twitter.com/realjustinclift
>>
>> _______________________________________________
>> Gluster-devel mailing list
>> Gluster-devel at gluster.org
>> http://supercolony.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20140904/02ac8c0e/attachment-0001.html>
More information about the Gluster-devel
mailing list