<div dir="ltr"><div><div>Hi Santosh,<br><br></div>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.<br><br></div>
Thanks,<br>Kiran.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 4, 2014 at 4:19 PM, Santosh Pradhan <span dir="ltr"><<a href="mailto:spradhan@redhat.com" target="_blank">spradhan@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
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).<br>
<br>
Thanks,<br>
Santosh<div><div class="h5"><br>
<br>
<br>
On 09/04/2014 03:34 PM, Justin Clift wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
On 28/08/2014, at 9:30 AM, Kiran Patil wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Gluster Devs,<br>
<br>
I ran the Gluster Test Framework on Gluster+zfs stack and found issues.<br>
<br>
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?<br>
</blockquote>
Definitely create an issue on the Red Hat Bugzilla, for the "GlusterFS"<br>
"product" ;> there:<br>
<br>
<a href="https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS" target="_blank">https://bugzilla.redhat.com/<u></u>enter_bug.cgi?product=<u></u>GlusterFS</a><br>
<br>
Since it's for the upstream Community, the official Red Hat "Supported"<br>
list isn't super relevant.<br>
<br>
<br>
<snip><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Test Summary Report<br>
-------------------<br>
./tests/basic/quota.t (Wstat: 0 Tests: 45 Failed: 3) --> quota issue<br>
Failed tests: 24, 28, 32<br>
./tests/bugs/bug-1004744.t (Wstat: 0 Tests: 14 Failed: 4) --> passes on changing EXPECT_WITHIN 20 to EXPECT_WITHIN 30<br>
Failed tests: 10, 12-14<br>
./tests/bugs/bug-1023974.t (Wstat: 0 Tests: 15 Failed: 1) --> quota issue<br>
Failed test: 12<br>
./tests/bugs/bug-824753.t (Wstat: 0 Tests: 16 Failed: 1) --> file-locker issue<br>
Failed test: 11<br>
./tests/bugs/bug-856455.t (Wstat: 0 Tests: 8 Failed: 1) --> brick directory name is hardcoded while executing kill command<br>
Failed test: 8<br>
./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};<br>
Failed test: 8<br>
./tests/bugs/bug-861542.t (Wstat: 0 Tests: 13 Failed: 4) --> brick directory name is hardcoded and all EXPECT tests are failing<br>
Failed tests: 10-13<br>
./tests/bugs/bug-902610.t (Wstat: 0 Tests: 8 Failed: 1) --> brick directory name is hardcoded and EXPECT test failing<br>
Failed test: 8<br>
./tests/bugs/bug-948729/bug-<u></u>948729-force.t (Wstat: 0 Tests: 35 Failed: 4) --> XFS related and brick directory name is hardcoded<br>
Failed tests: 15, 17, 19, 21<br>
./tests/bugs/bug-948729/bug-<u></u>948729-mode-script.t (Wstat: 0 Tests: 35 Failed: 8) --> XFS related and brick directory name is hardcoded<br>
Failed tests: 15, 17, 19, 21, 24-27<br>
./tests/bugs/bug-948729/bug-<u></u>948729.t (Wstat: 0 Tests: 23 Failed: 3) --> XFS related and brick directory name is hardcoded<br>
Failed tests: 12, 15, 23<br>
./tests/bugs/bug-963541.t (Wstat: 0 Tests: 13 Failed: 3) --> remove-brick issue<br>
Failed tests: 8-9, 13<br>
./tests/features/glupy.t (Wstat: 0 Tests: 6 Failed: 2)<br>
Failed tests: 2, 6<br>
<br>
Subset of the above bugs which can be reproduced on Glusterfs + ext4 is filed at Redhat bugzilla which is Bug id 1132496.<br>
</blockquote>
The glupy.t one I'll be able to look at, but not in the next few days. I need<br>
to finish my current task, and then to get my head back into Glupy.<br>
<br>
bug-1004744.t and the tests with hard coded brick directory names may be easy<br>
to fix. The others I'm not sure about.<br>
<br>
Do you have any interest in creating the fixes for the one's you're<br>
comfortable with, and submitting them through Gerrit? (<a href="http://review.gluster.org" target="_blank">review.gluster.org</a>)<br>
<br>
Regards and best wishes,<br>
<br>
Justin Clift<br>
<br>
--<br>
GlusterFS - <a href="http://www.gluster.org" target="_blank">http://www.gluster.org</a><br>
<br>
An open source, distributed file system scaling to several<br>
petabytes, and handling thousands of clients.<br>
<br>
My personal twitter: <a href="http://twitter.com/realjustinclift" target="_blank">twitter.com/realjustinclift</a><br>
<br></div></div>
______________________________<u></u>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://supercolony.gluster.<u></u>org/mailman/listinfo/gluster-<u></u>devel</a><br>
</blockquote>
<br>
</blockquote></div><br></div>