Re: [Gluster-devel] Gluster Test Framwork tests failed on Gluster+Zfs(Zfs on linux)
On 2014-09-04 13:08, Kaleb KEITHLEY wrote: > On 09/04/2014 06:49 AM, Santosh Pradhan 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. >>> > > There is no officially blessed file system for Community GlusterFS. > The only requirement is that the file system support extended > attributes. And that it does not use 64-bit offsets, as can be seen in http://supercolony.gluster.org/pipermail/gluster-devel/2014-July/041604.html I've had bad experiences with replication and ext4 :-( The design considerations in https://bugzilla.redhat.com/show_bug.cgi?id=838784 are to me quite dubious: However both these filesystmes (EXT4 more importantly) are "tolerant" in terms of the accuracy of the value presented back in seekdir(). i.e, a seekdir(val) actually seeks to the entry which has the "closest" true offset. This "two-prong" scheme exploits this behavior - which seems to be the best middle ground amongst various approaches and has all the advantages of the old approach: - Works against XFS and EXT4, the two most common filesystems out there. (which wasn't an "advantage" of the old approach as it is borken against EXT4) - Probably works against most of the others as well. The ones which would NOT work are those which return HUGE d_offs _and_ NOT tolerant to seekdir() to "closest" true offset. > > As a guide to best practice, you may wish to look at what Red Hat > officially supports for RHS GlusterFS — that is XFS. As you might > expect, that gets the most testing and likely has the fewest bugs > related to it. But people are successfully using other file systems, > e.g. ffs on NetBSD and FreeBSD, HFS+ on Mac OS X, and btrfs and zfs > on Linux. > > You may certainly file bugs against Community GlusterFS with zfs. I > will warn you though that due to various legal and political > realities, probably (certainly) none of the Red Hat employees that > work on GlusterFS will be able to devote time to it. > > If you fix the bugs you find, please submit your fix in Gerrit. We > will certainly accept fixes for legitimate bugs regardless of which > file system you use. Our development workflow is described here > http://www.gluster.org/community/documentation/index.php/Development_Work_Flow. > /Anders -- Anders Blomdell Email: anders.blomd...@control.lth.se Department of Automatic Control Lund University Phone:+46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Gluster Test Framwork tests failed on Gluster+Zfs(Zfs on linux)
On 09/04/2014 06:49 AM, Santosh Pradhan 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. There is no officially blessed file system for Community GlusterFS. The only requirement is that the file system support extended attributes. As a guide to best practice, you may wish to look at what Red Hat officially supports for RHS GlusterFS — that is XFS. As you might expect, that gets the most testing and likely has the fewest bugs related to it. But people are successfully using other file systems, e.g. ffs on NetBSD and FreeBSD, HFS+ on Mac OS X, and btrfs and zfs on Linux. You may certainly file bugs against Community GlusterFS with zfs. I will warn you though that due to various legal and political realities, probably (certainly) none of the Red Hat employees that work on GlusterFS will be able to devote time to it. If you fix the bugs you find, please submit your fix in Gerrit. We will certainly accept fixes for legitimate bugs regardless of which file system you use. Our development workflow is described here http://www.gluster.org/community/documentation/index.php/Development_Work_Flow. Regards, -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Gluster Test Framwork tests failed on Gluster+Zfs(Zfs on linux)
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 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.
>>
>>
>>
>>
>>> 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..1};
>>>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@gluster.org
>> http://supercolony.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Gluster Test Framwork tests failed on Gluster+Zfs(Zfs on linux)
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.
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..1};
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@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Gluster Test Framwork tests failed on Gluster+Zfs(Zfs on linux)
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.
> 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..1};
> 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@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Gluster Test Framwork tests failed on Gluster+Zfs(Zfs on linux)
Hi, Please let us know if there are any fixes to the gluster test framework. Any help/guidance on what should we do or can be done ? Thanks, Kiran. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Gluster Test Framwork tests failed on Gluster+Zfs(Zfs on linux)
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?
We modified the paths in include.rc to make sure that mount points and
bricks directories are created under the zfs datasets.
For example: include.rc first line
Original path -> M0=${M0:=/mnt/glusterfs/0}; # 0th mount point for FUSE
New path -> M0=${M0:=/fractalpool/normal/mnt/glusterfs/0}; # 0th mount
point for FUSE
Where /fractalpool is zfs pool and normal is zfs dataset.
Gluster version: v3.5.2
Zfs version: v0.6.2-1
Hardware: x86_64
How reproducible: Always
Steps to Reproduce:
1. Install gluster v3.5.2 rpm on CentOS 6.4
2. Install zfsonlinux v0.6.2
3. clone the gluster from github and checkout v3.5.2
4. ./run-tests.sh
Here is a summary of Testcases failed, along with some hints on where they
failed.
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..1};
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.
Thanks,
Kiran.
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
