Re: [Gluster-devel] Messup with peer status!!

On 03/15/2016 10:54 AM, ABHISHEK PALIWAL wrote: > Hi Atin, > > Is these files are ok? or you need some other files. I just started going through the log files you shared. I've few questions for you looking at the log: 1. Are you sure the log what you have provided from board B is post a reboot?

Re: [Gluster-devel] [master] FAILED: NetBSD regression for tests/performance/open-behind.t

Thanks manu. -- Milind - Original Message - From: "Emmanuel Dreyfus" To: "Milind Changire" , gluster-devel@gluster.org Sent: Tuesday, March 15, 2016 8:12:09 AM Subject: Re: [Gluster-devel] [master] FAILED: NetBSD regression for

Re: [Gluster-devel] [IMPORTANT] Release planning for GlusterFS 3.8, schedule, deadlines and all

On Mon, Mar 14, 2016 at 08:44:06PM +0530, Atin Mukherjee wrote: > -Atin > Sent from one plus one > On 14-Mar-2016 6:45 pm, "Niels de Vos" wrote: > > > > On Mon, Mar 14, 2016 at 05:54:00PM +0530, Atin Mukherjee wrote: > > > > > > > > > On 03/14/2016 02:49 PM, Niels de Vos wrote:

[Gluster-devel] Fragment size in Systematic erasure code

Hi Xavi, I think for Systematic erasure coded volume you are going to take fragment size of 512 Bytes. Will there be any CLI option to configure this block size? We were having a discussion and Manoj was suggesting to have this option which might improve performance for some workload. For

Re: [Gluster-devel] [IMPORTANT] Release planning for GlusterFS 3.8, schedule, deadlines and all

On Mon, Mar 14, 2016 at 05:54:00PM +0530, Atin Mukherjee wrote: > > > On 03/14/2016 02:49 PM, Niels de Vos wrote: > > Hi, > > > > We're kicking the 3.8 release back into shape and schedule. Our planned > > 6 month release cycle has completely failed on us, we're about 6 months > > behind. I've

Re: [Gluster-devel] Fragment size in Systematic erasure code

Hi Xavi, - Original Message - > From: "Xavier Hernandez" > To: "Ashish Pandey" > Cc: "Gluster Devel" , "Manoj Pillai" > > Sent: Monday, March 14, 2016 5:25:53 PM > Subject: Re: Fragment size in

Re: [Gluster-devel] 3.7.9 update

On 14 March 2016 at 14:29, Raghavendra Talur wrote: > > > On Mon, Mar 14, 2016 at 8:40 AM, Kaushal M wrote: > >> Hey Vijay, >> >> Awesome work on the tests! >> > +1 > > > >> >> Could you please list down the tests you run for releases? This would >> help

Re: [Gluster-devel] Messup with peer status!!

On 03/14/2016 05:09 PM, ABHISHEK PALIWAL wrote: > I am not getting you which glusterd directory you are asking. if you are > asking about the /var/lib/glusterd directory then which I shared earlier > is the same. 1. Go to /var/log/glusterfs directory 2. Look for glusterd log file 3. attach the

Re: [Gluster-devel] Messup with peer status!!

even /var/log/glusterfs directory logs are also present in 00300/glusterfs and 002500/glusterfs. Regards, Abhishek On Mon, Mar 14, 2016 at 5:09 PM, ABHISHEK PALIWAL wrote: > I am not getting you which glusterd directory you are asking. if you are > asking about the

Re: [Gluster-devel] Fragment size in Systematic erasure code

Hi Ashish, On 14/03/16 12:31, Ashish Pandey wrote: Hi Xavi, I think for Systematic erasure coded volume you are going to take fragment size of 512 Bytes. Will there be any CLI option to configure this block size? We were having a discussion and Manoj was suggesting to have this option which

Re: [Gluster-devel] Messup with peer status!!

I am not getting you which glusterd directory you are asking. if you are asking about the /var/lib/glusterd directory then which I shared earlier is the same. I have two directories related to gluster 1. /var/log/glusterfs 2./var/lib/glusterd On Mon, Mar 14, 2016 at 4:12 PM, Atin Mukherjee

[Gluster-devel] [IMPORTANT] Release planning for GlusterFS 3.8, schedule, deadlines and all

Hi, We're kicking the 3.8 release back into shape and schedule. Our planned 6 month release cycle has completely failed on us, we're about 6 months behind. I've taken the liberty to set aggressive deadlines and put this on the roadmap on https://www.gluster.org/community/roadmap/3.8/ . The page

Re: [Gluster-devel] Messup with peer status!!

On 03/14/2016 03:59 PM, ABHISHEK PALIWAL wrote: > I have only these glusterd files available on the nodes Look for etc-*-glusterd*.log in /var/log/glusterfs, that represents the glusterd log file. > > Regards, > Abhishek > > On Mon, Mar 14, 2016 at 3:43 PM, Atin Mukherjee

Re: [Gluster-devel] Messup with peer status!!

I have only these glusterd files available on the nodes Regards, Abhishek On Mon, Mar 14, 2016 at 3:43 PM, Atin Mukherjee wrote: > > > On 03/14/2016 02:18 PM, ABHISHEK PALIWAL wrote: > > > > > > On Mon, Mar 14, 2016 at 12:12 PM, Atin Mukherjee >

[Gluster-devel] [master] FAILED: NetBSD regression for tests/performance/open-behind.t

https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/15170/ [06:30:49] Running tests in file ./tests/performance/open-behind.t tar: Failed open to read/write on

Re: [Gluster-devel] Query on healing process

On 03/14/2016 10:36 AM, ABHISHEK PALIWAL wrote: Hi Ravishankar, I just want to inform that this file have some different properties from other files like this is the file which having the fixed size and when there is no space in file the next data will start wrapping from the top of the

Re: [Gluster-devel] NetBSD Regression failure on 3.7: ./tests/features/trash.t

On Mon, Mar 14, 2016 at 12:08:31PM +0530, Anoop C S wrote: > Test #59 is a volume heal command: > TEST $CLI volume heal $V1 > I am not sure why this command itself failed. Let me take a look > through the archived logs. It would not be the first time an unrelated bug pops up where we do not

Re: [Gluster-devel] Code profiling tool

On Mon, Mar 14, 2016 at 11:48:41AM +0800, jayakrishnan mm wrote: > Hi > > I want to profile some part of the source code in glsuterfs. Can > anybody suggest some tool ? For source code, you probably want to look into "strace -c" or its "ltrace" equivalent. Perf would also be an option. If

Re: [Gluster-devel] Messup with peer status!!

On 03/14/2016 10:52 AM, ABHISHEK PALIWAL wrote: > Hi Team, > > I am facing some issue with peer status and because of that remove-brick > on replica volume is getting failed. > > Here. is the scenario what I am doing with gluster: > > 1. I have two boards A & B and gluster is running on both

Re: [Gluster-devel] NetBSD Regression failure on 3.7: ./tests/features/trash.t

On Mon, 2016-03-14 at 02:23 -0400, Kotresh Hiremath Ravishankar wrote: > Hi, > > trash.t is failing on 3.7 branch for below patch. > > https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/ > 15153/console > Running tests in file ./tests/features/trash.t [15:25:43]

[Gluster-devel] NetBSD Regression failure on 3.7: ./tests/features/trash.t

Hi, trash.t is failing on 3.7 branch for below patch. https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/15153/console Could someone look into it? Thanks and Regards, Kotresh H R ___ Gluster-devel mailing list

Re: [Gluster-devel] Bitrot/Tering : Bad files get migrated and hence corruption goes undetected.

On Wed, Mar 02, 2016 at 02:13:59PM +0530, Venky Shankar wrote: > On Wed, Mar 02, 2016 at 11:43:50AM +0530, Venky Shankar wrote: > > On Sat, Feb 27, 2016 at 06:32:38AM -0500, Joseph Fernandes wrote: > > > Yep Agree! :) > > > > > > Lets hear from the bitrot folks, what they have to propose. > > >