Re: [Gluster-devel] rm -r problem on FreeBSD port

Sakshi Bansal wrote: > > However, other times, the "rm" doesn't report an error, but the file > > remains > > visible via "ls" and the rmdir fails. > when this case happens does the ls show a linkto file or the original data > file. > It sometimes shows a single entry and sometimes two entries,

Re: [Gluster-devel] Troubleshooting and Diagnostic tools for Gluster

Nice tool. Easy to add, clone the glustertool repo, and run # ./newtool mnt_log_analyze --type=exec --bin=log_analyzer.sh --prog=bash I used tool name "mnt_log_analyze" just for this example, feel free to name your tool. This will create following dir and files

Re: [Gluster-devel] Troubleshooting and Diagnostic tools for Gluster

I have a script written to analyze the log message of gluster process. It actually scans the log file and identifies the log messages with ERROR and WARNING levels. It lists the functions (with either ERROR or WARNING logs) and their percentage of occcurance. It also lists the MSGIDs for ERROR

Re: [Gluster-devel] rm -r problem on FreeBSD port

I wrote: > Sakshi Bansal wrote: > > > However, other times, the "rm" doesn't report an error, but the file > > > remains > > > visible via "ls" and the rmdir fails. > > when this case happens does the ls show a linkto file or the original data > > file. > > > It sometimes shows a single entry and

Re: [Gluster-devel] [Gluster-infra] Different version of run-tests.sh in jenkin slaves?

On Thu, Jan 28, 2016 at 11:17 AM, Atin Mukherjee wrote: > Are we running a different version of run-tests.sh in jenkin slaves. The > reason of suspection is beacuse in last couple of runs [1] & [2] in > NetBSD I am seeing no failures apart from bad tests but the regression >

Re: [Gluster-devel] patch #10954

> If anything is going in mainline I'd encourage the same to be backported > irrespective of the severity of the fix, so that's out of the equation. Will keep this is mind in future. > I'd like to stick to remove brick_up_status(). Please use the same in > all the places. You can include all

Re: [Gluster-devel] [Gluster-infra] Different version of run-tests.sh in jenkin slaves?

On 01/28/2016 12:00 PM, Raghavendra Talur wrote: > Ok, RCA: > > In NetBSD cores are being generated in /d/backends/*/*.core > run-tests.sh looks only for "/core*" when looking for cores. > > So, at the end of test run when regression.sh looks for core everywhere, > it finds one and errors out.

Re: [Gluster-devel] patch #10954

On 01/28/2016 09:57 AM, Sakshi Bansal wrote: > >> If anything is going in mainline I'd encourage the same to be backported >> irrespective of the severity of the fix, so that's out of the equation. > Will keep this is mind in future. > > >> I'd like to stick to remove brick_up_status().

Re: [Gluster-devel] Throttling xlator on the bricks

On 01/26/2016 08:41 AM, Richard Wareing wrote: In any event, it might be worth having Shreyas detail his throttling feature (that can throttle any directory hierarchy no less) to illustrate how a simpler design can achieve similar results to these more complicated (and it followsbug

Re: [Gluster-devel] [Gluster-infra] Different version of run-tests.sh in jenkin slaves?

Ok, RCA: In NetBSD cores are being generated in /d/backends/*/*.core run-tests.sh looks only for "/core*" when looking for cores. So, at the end of test run when regression.sh looks for core everywhere, it finds one and errors out. Should think of a solution which is generic. Will update. On

Re: [Gluster-devel] Throttling xlator on the bricks

There is already a patch submitted for moving TBF part to libglusterfs. It is under review. http://review.gluster.org/#/c/12413/ Regards, Raghavendra On Mon, Jan 25, 2016 at 2:26 AM, Venky Shankar wrote: > On Mon, Jan 25, 2016 at 11:06:26AM +0530, Ravishankar N wrote: > >

Re: [Gluster-devel] Troubleshooting and Diagnostic tools for Gluster

Also, don't forget to send a pull request to Aravinda, so that others can use it too. Maybe add some basic usage note. If it is not already there. On Thu, Jan 28, 2016 at 7:04 AM, Aravinda wrote: > Nice tool. > > Easy to add, clone the glustertool repo, and run > > #

Re: [Gluster-devel] patch #10954

On Wed, Jan 27, 2016 at 11:27:26PM -0500, Sakshi Bansal wrote: > > > If anything is going in mainline I'd encourage the same to be backported > > irrespective of the severity of the fix, so that's out of the equation. > Will keep this is mind in future. > > > > I'd like to stick to remove

Re: [Gluster-devel] [Gluster-infra] Different version of run-tests.sh in jenkin slaves?

On Thu, Jan 28, 2016 at 12:10 PM, Atin Mukherjee wrote: > > > On 01/28/2016 12:00 PM, Raghavendra Talur wrote: > > Ok, RCA: > > > > In NetBSD cores are being generated in /d/backends/*/*.core > > run-tests.sh looks only for "/core*" when looking for cores. > > > > So, at the

Re: [Gluster-devel] [Gluster-Maintainers] Patches for supporting lseek() with SEEK_DATA/SEEK_HOLE available for review

On Wed, Jan 27, 2016 at 5:34 PM, Niels de Vos wrote: > Hi all, > > yesterday I have posted the latest version of a series that implements > support for lseek() with SEEK_DATA/SEEK_HOLE. This functionality can > improve the handling of sparse files immensely. > > Please review

[Gluster-devel] Different version of run-tests.sh in jenkin slaves?

Are we running a different version of run-tests.sh in jenkin slaves. The reason of suspection is beacuse in last couple of runs [1] & [2] in NetBSD I am seeing no failures apart from bad tests but the regression voted failure and I can not make out any valid reason out of it. [1]

[Gluster-devel] Patches for supporting lseek() with SEEK_DATA/SEEK_HOLE available for review

Hi all, yesterday I have posted the latest version of a series that implements support for lseek() with SEEK_DATA/SEEK_HOLE. This functionality can improve the handling of sparse files immensely. Please review the changes that involve components if your interest:

Re: [Gluster-devel] Simple way to re-trigger jenkins jobs

On Wed, Jan 27, 2016 at 12:02:52PM +0530, Raghavendra Talur wrote: > Hi, > > Prashanth informed about a simple way to let every contributor retrigger > the regression runs that openstack uses. > > We have implemented same for gluster. Trigger comments are: > > recheck netbsd > recheck smoke >

Re: [Gluster-devel] [Gluster-users] GlusterFS FUSE client hangs on rsyncing lots of file

Hi, If the hang appears on enabling client side io-threads then it could be because of some race that is seen when io-threads is enabled on the client side. 2 things will help us debug this issue: 1) thread apply all bt inside gdb (with debuginfo rpms/debs installed ) 2) Complete

Re: [Gluster-devel] [Gluster-users] Gluster Monthly Newsletter, January 2015 Edition

On 22 January 2016 at 22:59, Niels de Vos wrote: > On Mon, Jan 18, 2016 at 07:46:16PM -0800, Amye Scavarda wrote: > > We're kicking off an updated Monthly Newsletter, coming out mid-month. > > We'll highlight special posts, news and noteworthy threads from the > > mailing

[Gluster-devel] Gluster community weekly meeting MoM

Minutes: http://meetbot.fedoraproject.org/gluster-meeting/2016-01-27/gluster_community_weekly_meeting.2016-01-27-12.00.html Minutes (text): http://meetbot.fedoraproject.org/gluster-meeting/2016-01-27/gluster_community_weekly_meeting.2016-01-27-12.00.txt Log: