Re: [Gluster-devel] [Gluster-Maintainers] GlusterFS 3.9 release Schedule
On Fri, Sep 9, 2016 at 5:16 PM, Aravindawrote: > Hi All, > > Gluster 3.9 release Schedule > > Week of Sept 12-16 - Beta Tagging and Start testing > Week of Sept 19-23 - RC tagging > End of Sept 2016 - GA(General Availability) release of 3.9 > > Considering that beta tagging will be done in next week, is it okay to > accept any features(Which are already Merged in Master) in release-3.9 > branch till Sept 12? > > Other tasks before GA: > - Removing or disabling incomplete features or the features which are not > ready > - Identifying Packaging issues for different distributions > - Documenting the release process so that it will be helpful for new > maintainers > - Release notes preparation > - Testing and Documentation completeness checking. > - Blog about the release > > Comments and Suggestions are Welcome. > > @Pranith, please add if missed anything. > Looks fine :-) > > Thanks > Aravinda & Pranith > ___ > maintainers mailing list > maintain...@gluster.org > http://www.gluster.org/mailman/listinfo/maintainers > -- Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Checklist for Bitrot component for upstream release
I would recommend the following tests. 1) The tests in our regression tests 2) Creating data set of many files (of different sizes) and then enabling bit-rot on the volume. 3) scrubber throttling 4) Tests such as open + write + close and again open + write + close (i.e. before the bit-rot daemon can sign the file the file is modified again) 5) Exceed the lru size of the inode table. (So that inodes are forgotten). The next lookup of the file should properly populate all the necessary details into the inode context. 6) Simulating the corruption by directly changing a file in the backend and checking if its marked as bad or not. (Also access to such bad files should give EIO) 7) Change scrubbing intervals and check if it kicks in correctly. Kotresh, Can you please add any other tests that should be considered? Regards, Raghavendra On Fri, Sep 2, 2016 at 2:25 PM, Pranith Kumar Karampuriwrote: > > > On Fri, Sep 2, 2016 at 11:39 PM, Pranith Kumar Karampuri < > pkara...@redhat.com> wrote: > >> hi, >> Did you get a chance to decide on the tests that need to be done >> before doing a release for Bitrot component? Could you let me know who will >> be providing with the list? >> >> I can update it at https://public.pad.fsfe.org/p/ >> gluster-component-release-checklist >> >> -- >> Pranith >> > Sorry, forgot to add 'Aravinda & Pranith' > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Trash test aborted netbsd regression
Hi Atin, From the console log: 01:22:55 rm: /mnt/glusterfs/0/abc/internal_op: Operation not permitted 01:22:55 rm: /mnt/glusterfs/0/abc: Directory not empty 01:22:55 mv: rename /mnt/glusterfs/0/abc to /mnt/glusterfs/0/trash: Operation not permitted 05:09:06 Build timed out (after 300 minutes). Marking the build as aborted. rename is the last test case in trash.t and it got executed successfully. snippet from trash.t TEST [ -e $M0/abc ] mv $M0/abc $M0/trash TEST [ -e $M0/abc ] cleanup So it may hung either TEST [-e $MO/abc] or in cleanup. IMHO possibility of TEST [-e $M0/abc] getting time out much less when compared to cleanup. Regards, Jiffin On 09/09/16 18:34, Atin Mukherjee wrote: http://build.gluster.org/job/netbsd7-regression/634/ (I had observed same failure earlier as well but didnt have link) -- --Atin ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Trash test aborted netbsd regression
http://build.gluster.org/job/netbsd7-regression/634/ (I had observed same failure earlier as well but didnt have link) -- --Atin ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Gluster and FreeBSD
Hi, I recently debugged a problem [1] where linkfiles were not created properly a gluster volume created using bricks running UFS . Whenever a linkfile was created, the sticky bit was not set on it causing the same file to be listed twice. >From https://www.freebsd.org/cgi/man.cgi?query=chmod=2 The FreeBSD VM system totally ignores the sticky bit (S_ISVTX) for executables. On UFS-based file systems (FFS, LFS) the sticky bit may only be set upon directories. Based on this I do not think we can support UFS bricks for gluster volumes. However, I have not worked with FreeBSD so I would like folks who have to let me know if this is correct or if there is something I am missing. I was able to force the sticky bit on a file using a testfile attached to [1] but it is not straightforward and I am reluctant to propose this. Thanks, Nithya [1] https://bugzilla.redhat.com/show_bug.cgi?id=1176011 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] GlusterFS 3.9 release Schedule
Hi All, Gluster 3.9 release Schedule Week of Sept 12-16 - Beta Tagging and Start testing Week of Sept 19-23 - RC tagging End of Sept 2016 - GA(General Availability) release of 3.9 Considering that beta tagging will be done in next week, is it okay to accept any features(Which are already Merged in Master) in release-3.9 branch till Sept 12? Other tasks before GA: - Removing or disabling incomplete features or the features which are not ready - Identifying Packaging issues for different distributions - Documenting the release process so that it will be helpful for new maintainers - Release notes preparation - Testing and Documentation completeness checking. - Blog about the release Comments and Suggestions are Welcome. @Pranith, please add if missed anything. Thanks Aravinda & Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Libunwind
On Thu, Sep 08, 2016 at 09:07:33AM -0400, Jeff Darcy wrote: > (1) Has somebody already gone down this path? Does it work? I recall attempting to port the Julia programming language to NetBSD, and libunwind gave me a hard time because the NetBSD does not implement an API as large as on Linux. My advice is to review supported platfrom's header file before using some feature, otherwise the result will not be easily portable -- Emmanuel Dreyfus m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel