Re: [Gluster-devel] Not able to compile glusterfs

Thanks that helps. On Mon, Mar 27, 2017 at 8:21 AM, Ravishankar N <ravishan...@redhat.com> wrote: > On 03/27/2017 06:30 AM, Pranith Kumar Karampuri wrote: > > hi, > When I compile I get the following errors: > > EC dynamic support : x64 sse avx > Use memory poo

Re: [Gluster-devel] Maintainers 2.0 Proposal

On Sat, Mar 18, 2017 at 1:20 AM, Amar Tumballi wrote: > I don't want to take the discussions in another direction, but want > clarity on few things: > > 1. Does maintainers means they are only reviewing/ merging patches? > 2. Should maintainers be responsible for answering

Re: [Gluster-devel] Consistent time attributes (ctime, atime and mtime) across replica set and distribution set

On Wed, Mar 15, 2017 at 11:31 PM, Soumya Koduri wrote: > Hi Rafi, > > I haven't thoroughly gone through design. But have few comments/queries > which I have posted inline for now . > > On 02/28/2017 01:11 PM, Mohammed Rafi K C wrote: > >> Thanks for the reply , Comments are

Re: [Gluster-devel] [Gluster-users] Glusterfs meta data space consumption issue

Is your backend filesystem ext4? On Thu, Apr 13, 2017 at 6:29 AM, ABHISHEK PALIWAL wrote: > No,we are not using sharding > On Apr 12, 2017 7:29 PM, "Alessandro Briosi" wrote: > >> Il 12/04/2017 14:16, ABHISHEK PALIWAL ha scritto: >> >> I have did more

Re: [Gluster-devel] [Gluster-users] Glusterfs meta data space consumption issue

Yes On Thu, Apr 13, 2017 at 8:21 AM, ABHISHEK PALIWAL <abhishpali...@gmail.com> wrote: > Means the fs where this brick has been created? > On Apr 13, 2017 8:19 AM, "Pranith Kumar Karampuri" <pkara...@redhat.com> > wrote: > >> Is your backend filesystem ext

Re: [Gluster-devel] [Gluster-users] Glusterfs meta data space consumption issue

but not sure if it is fixed in ext4 in the latest releases. > > On Thu, Apr 13, 2017 at 9:26 AM, Pranith Kumar Karampuri < > pkara...@redhat.com> wrote: > >> Yes >> >> On Thu, Apr 13, 2017 at 8:21 AM, ABHISHEK PALIWAL < >> abhishpali...@gmail.com> wrote: >&

Re: [Gluster-devel] [Gluster-users] High load on glusterfsd process

+Kotresh who seems to have worked on the bug you mentioned. On Fri, Apr 21, 2017 at 12:21 PM, ABHISHEK PALIWAL wrote: > > If the patch provided in that case will resolve my bug as well then please > provide the patch so that I will backport it on 3.7.6 > > On Fri, Apr

Re: [Gluster-devel] fstest for fuse mount gluster

we can remove the reliance on S+T bits. Worst case we will have to store the info on the xattr. > > regards, > Raghavendra. > > - Original Message - > > From: "Pranith Kumar Karampuri" <pkara...@redhat.com> > > To: "qingwei wei"

Re: [Gluster-devel] fstest for fuse mount gluster

This is a bug in dht it seems like. It is stripping PHASE1 flags unconditionally. (gdb) 1212DHT_STRIP_PHASE1_FLAGS (>stbuf); (gdb) p local->stbuf.ia_prot $18 = { suid = 1 '\001', sgid = 1 '\001', <--- sticky = 1 '\001', <--- . } (gdb) n 1213

Re: [Gluster-devel] [master] [FAILED] [centos6] tests/bitrot/bug-1373520.t

Following patch fixed this already, I just rebased your change. commit a2d4c928e93c95dfe2ceff450556f8494d67e654 Author: Krutika Dhananjay Date: Wed Mar 1 12:48:10 2017 +0530 storage/posix: Set ret value correctly before exiting Change-Id:

Re: [Gluster-devel] gfid and volume-id extended attributes lost

On Fri, Jul 7, 2017 at 9:15 PM, Pranith Kumar Karampuri <pkara...@redhat.com > wrote: > Did anything special happen on these two bricks? It can't happen in the > I/O path: > posix_removexattr() has: > 0 if (!strcmp (GFID_XATTR_KEY, name)) > { > > > 1

Re: [Gluster-devel] gfid and volume-id extended attributes lost

e issue. The bricks were > mounted after the reboot. One more thing that I noticed was when the > attributes were manually set when glusterd was up then on starting the > volume the attributes were again lost. Had to stop glusterd set attributes > and then start glusterd. After that the volume sta

Re: [Gluster-devel] gfid and volume-id extended attributes lost

when glusterd was up then on starting the > volume the attributes were again lost. Had to stop glusterd set attributes > and then start glusterd. After that the volume start succeeded. > Which version is this? > > > Thanks and Regards, > > Ram > > > > *From:* Pra

Re: [Gluster-devel] gfid and volume-id extended attributes lost

Did anything special happen on these two bricks? It can't happen in the I/O path: posix_removexattr() has: 0 if (!strcmp (GFID_XATTR_KEY, name)) { 1 gf_msg (this->name, GF_LOG_WARNING, 0, P_MSG_XATTR_NOT_REMOVED, 2 "Remove xattr called on gfid

[Gluster-devel] crash in tests/bugs/core/bug-1432542-mpx-restart-crash.t

I just observed that https://build.gluster.org/job/centos6-regression/5433/consoleFull failed because of this .t failure. -- Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] Build failed in Jenkins: regression-test-with-multiplex #162

Ah! sorry, I need to keep this in mind next time when I review. On Mon, Jul 17, 2017 at 6:30 PM, Atin Mukherjee wrote: > kill $pid0 > > kill $pid1 > > EXPECT_WITHIN $CHILD_UP_TIMEOUT "4" ec_child_up_count $V0 0 > > *21:03:33* not ok 17 Got "0" instead of "4",

Re: [Gluster-devel] GlusterFS v3.12 - Nearing deadline for branch out

hi, Status of the following features targeted for 3.12: 1) Need a way to resolve split-brain (#135) : Mostly will be merged in a day. 2) Halo Hybrid mode (#217): Unfortunately didn't get time to follow up on this, so will not make it to the release. 3) Implement heal throttling (#255):

Re: [Gluster-devel] gfid and volume-id extended attributes lost

glusterfs6sds.commvault.com:/ws/disk8/ws_brick > > Brick58: glusterfs4sds.commvault.com:/ws/disk9/ws_brick > > Brick59: glusterfs5sds.commvault.com:/ws/disk9/ws_brick > > Brick60: glusterfs6sds.commvault.com:/ws/disk9/ws_brick > > Options Reconfigured: > > perf

Re: [Gluster-devel] create restrictions xlator

hey, I went through the patch. I see that statfs is always wound for create fop. So number of network operations increase and performance will be less even in normal case. I think similar functionality is in DHT, may be you should take a look at that? Check dht_get_du_info() which is used

Re: [Gluster-devel] gfid and volume-id extended attributes lost

this out and let you know. > > > > Thanks and Regards, > > Ram > > *From:* Pranith Kumar Karampuri [mailto:pkara...@redhat.com] > *Sent:* Monday, July 10, 2017 8:31 AM > *To:* Sanoj Unnikrishnan > *Cc:* Ankireddypalle Reddy; Gluster Devel (gluster-devel@gluster.org)

Re: [Gluster-devel] create restrictions xlator

> - > Taehwa Lee > Gluesys Co.,Ltd. > alghost@gmail.com > +82-10-3420-6114, +82-70-8785-6591 > ----- > > 2017. 7. 13. 오후 1:06, Pranith Kumar Karampuri <pkara...@redhat.com> 작성: > > hey, &g

Re: [Gluster-devel] Forgot how to download NetBSD logfiles

On Fri, Jul 14, 2017 at 9:22 PM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > hi, >I am not able to download the "Logs archived in > http://nbslave74.cloud.gluster.org/archives/logs/ > glusterfs-logs-20170713080233.tgz" > > I get the followin

[Gluster-devel] Forgot how to download NetBSD logfiles

hi, I am not able to download the "Logs archived in http://nbslave74.cloud.gluster.org/archives/logs/glusterfs-logs-20170713080233.tgz " I get the following error: archives/logs/glusterfs-logs-20170713080233.tgz We had to modify something in the URL to get the correct link but now either

Re: [Gluster-devel] [Gluster-users] Replicated volume, one slow brick

Adding gluster-devel Raghavendra, I remember we discussing about handling these kinds of errors by ping-timer expiry? I may have missed the final decision on how this was decided to be handled. So asking you again ;-) On Thu, Jul 13, 2017 at 2:14 PM, Øyvind Krosby wrote:

Re: [Gluster-devel] Regarding positioning of nl-cache in gluster client stack

On Mon, Jul 17, 2017 at 11:31 AM, Krutika Dhananjay wrote: > Hi Poornima and Pranith, > > I see that currently glusterd loads nl-cache between stat-prefetch and > open-behind on the client stack. Were there any specific considerations for > selecting this position for

Re: [Gluster-devel] Error while mounting gluster volume

The following generally means it is not able to connect to any of the glusterds in the cluster. [1970-01-02 10:54:04.420406] E [glusterfsd-mgmt.c:1818:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: 128.224.95.140 (Success) [1970-01-02 10:54:04.420422] I [MSGID: 101190]

Re: [Gluster-devel] Changing the relative order of read-ahead and open-behind

On Mon, Jul 24, 2017 at 5:11 PM, Raghavendra G wrote: > > > On Fri, Jul 21, 2017 at 6:39 PM, Vijay Bellur wrote: > >> >> On Fri, Jul 21, 2017 at 3:26 AM, Raghavendra Gowdappa < >> rgowd...@redhat.com> wrote: >> >>> Hi all, >>> >>> We've a bug [1],

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

On Sat, Jul 22, 2017 at 1:36 AM, Shyam wrote: > Hi, > > Prepare for a lengthy mail, but needed for the 3.12 release branching, so > here is a key to aid the impatient, > > Key: > 1) If you asked for an exception to a feature (meaning delayed backport to > 3.12 branch post

Re: [Gluster-devel] Disperse volume : Sequential Writes

if possible. On Fri, Jun 16, 2017 at 4:19 PM, Ashish Pandey <aspan...@redhat.com> wrote: > > I think it should be done as we have agreement on basic design. > > -- > *From: *"Pranith Kumar Karampuri" <pkara...@redhat.com> > *To: *"Xa

Re: [Gluster-devel] geo-rep regression because of node-uuid change

hik > >> If no one can do it, I can try to do it in 6 - 7 hours... >> >> Xavi >> >> >> On Wednesday, June 21, 2017 09:48 CEST, Pranith Kumar Karampuri < >> pkara...@redhat.com> wrote: >> >> >> >> >> On Wed, Jun 21, 2017

Re: [Gluster-devel] Suggest how to recognize the time when heal is triggered by using events

patch looks good to me. Do you want to send it on gerrit? On Wed, Jul 5, 2017 at 6:49 AM, Taehwa Lee wrote: > Hello, Karampuri. > > > I've been developing products using glusterfs for 2 years almost with my > co-workers. > > I got a problem that the products cannot

Re: [Gluster-devel] Disperse volume : Sequential Writes

On Tue, Jul 4, 2017 at 1:39 PM, Xavier Hernandez <xhernan...@datalab.es> wrote: > Hi Pranith, > > On 03/07/17 05:35, Pranith Kumar Karampuri wrote: > >> Ashish, Xavi, >>I think it is better to implement this change as a separate >> read-after-write cach

Re: [Gluster-devel] geo-rep regression because of node-uuid change

On Tue, Jul 4, 2017 at 2:26 PM, Xavier Hernandez <xhernan...@datalab.es> wrote: > Hi Pranith, > > On 03/07/17 08:33, Pranith Kumar Karampuri wrote: > >> Xavi, >> Now that the change has been reverted, we can resume this >> discussion and decide on the ex

Re: [Gluster-devel] Glusto failures with dispersed volumes + Samba

On Thu, Jun 29, 2017 at 6:49 PM, Anoop C S wrote: > On Thu, 2017-06-29 at 16:35 +0530, Nigel Babu wrote: > > Hi Pranith and Xavi, > > > > We seem to be running into a problem with glusto tests when we try to > run them against dispersed > > volumes over a CIFS mount[1]. >

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

On Thu, Apr 13, 2017 at 8:17 PM, Shyam wrote: > On 02/28/2017 10:17 AM, Shyam wrote: > >> Hi, >> >> With release 3.10 shipped [1], it is time to set the dates for release >> 3.11 (and subsequently 4.0). >> >> This mail has the following sections, so please read or revisit as

Re: [Gluster-devel] Need inputs on patch #17985

gt; > *To: *"Ashish Pandey" <aspan...@redhat.com> > *Cc: *"Pranith Kumar Karampuri" <pkara...@redhat.com>, "Xavier Hernandez" > <xhernan...@datalab.es>, "Gluster Devel" <gluster-devel@gluster.org> > *Sent: *Wednesday, August

[Gluster-devel] Questions on github

hi, Wanted to know what people feel about asking/answering questions on github.com, at the moment we are only using github for RFEs, I am wondering if it would be fine to open it for questions too. Main benefit I see is that it is easier to see open-questions at a glance and easy to direct

Re: [Gluster-devel] Questions on github

to bugs/features/documentation we can take this route. We can always encourage them to post on gluster-users and close the question if it doesn't fall in the category. > > > Regards, > Amar > > On Tue, May 9, 2017 at 2:57 PM, Pranith Kumar Karampuri < > pkara...@redhat.com&g

Re: [Gluster-devel] [Gluster-users] 120k context switches on GlsuterFS nodes

+ gluster-devel On Wed, May 17, 2017 at 10:50 PM, mabi wrote: > I don't know exactly what kind of context-switches it was but what I know > is that it is the "cs" number under "system" when you run vmstat. > > Also I use the percona linux monitoring template for cacti ( >

Re: [Gluster-devel] Suggestion to optimize posix_getxattr call

yeah +1 from me too. On Mon, May 15, 2017 at 2:56 PM, Mohit Agrawal wrote: > Hi, > > I was just checking of posix_getxattr code to debug of my one problem.I > have found scope of improvement in > this function to execute system call in better way.As of now >

Re: [Gluster-devel] tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.t - regression failures

On Wed, May 17, 2017 at 4:34 PM, Ravishankar N <ravishan...@redhat.com> wrote: > On 05/17/2017 04:09 PM, Pranith Kumar Karampuri wrote: > > karthik, Ravi, > What is the plan to bring it back? Did you guys find RC for the > failure? > > Are you referring to gfid-m

Re: [Gluster-devel] Change in rebalance graph

AFR had similar problem 2 years back and we started persisting afr children and graph always gets generated with what the xattrs will be in that order as an option. You can check afr_pending_xattrs_init() for it. On the glusterd side we give an identifer for each of the bricks. The main reason we

Re: [Gluster-devel] tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.t - regression failures

karthik, Ravi, What is the plan to bring it back? Did you guys find RC for the failure? On Mon, May 15, 2017 at 10:52 AM, Ravishankar N wrote: > On 05/12/2017 03:33 PM, Atin Mukherjee wrote: > > tests/basic/afr/add-brick-self-heal.t >

Re: [Gluster-devel] Questions on github

st for questions it seems like a good idea to participate on github, so that if a question doesn't get answered we would at least know at some point and answer it. > Shyam > > On 05/09/2017 05:27 AM, Pranith Kumar Karampuri wrote: > >> hi, >> Wanted to know what people feel ab

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay < sankarshan.mukhopadh...@gmail.com> wrote: > On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi wrote: > > I personally prefer github questions than mailing list, because a valid > > question can later become a reason for a

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 7:27 PM, Sankarshan Mukhopadhyay < sankarshan.mukhopadh...@gmail.com> wrote: > On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri > <pkara...@redhat.com> wrote: > > > > > > On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay &g

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 9:01 PM, Sankarshan Mukhopadhyay < sankarshan.mukhopadh...@gmail.com> wrote: > On Tue, May 9, 2017 at 8:50 PM, Niels de Vos wrote: > > [much snipping] > > > A but related to this, but is Stack Overflow not *the* place to ask and > > answer questions?

Re: [Gluster-devel] [Qusetions] About the implemention of function gf_backtrace_fillframes

This is the patch which introduced this change, seems like the author wanted it work under memory pressure. I didn't read it carefully though. glusterd: Add last successful glusterd lock backtrace Also, moved the backtrace fetching logic to a separate function. Modified the backtrace

Re: [Gluster-devel] about deduplication feature

On Tue, Jun 20, 2017 at 7:29 AM, Li, Dan wrote: > Hi, all > > we are using GlusterFS to construct our distribute filesystem. > Does gulsterFS has the deduplication feature on volumes? > Will you support it in the future? > hi Lidan, At the moment, GlusterFS doesn't

Re: [Gluster-devel] geo-rep regression because of node-uuid change

On Wed, Jun 21, 2017 at 10:07 AM, Nithya Balachandran <nbala...@redhat.com> wrote: > > On 20 June 2017 at 20:38, Aravinda <avish...@redhat.com> wrote: > >> On 06/20/2017 06:02 PM, Pranith Kumar Karampuri wrote: >> >> Xavi, Aravinda and I had a discuss

Re: [Gluster-devel] geo-rep regression because of node-uuid change

y yesterday, but looks like this is what we are settling on) > > Xavi > > > On Wednesday, June 21, 2017 06:56 CEST, Pranith Kumar Karampuri < > pkara...@redhat.com> wrote: > > > > > On Wed, Jun 21, 2017 at 10:07 AM, Nithya Balachandran <nbala...@red

Re: [Gluster-devel] geo-rep regression because of node-uuid change

Kotresh and Aravinda, >> >> On 20/06/17 09:45, Pranith Kumar Karampuri wrote: >> >>> >>> >>> On Tue, Jun 20, 2017 at 1:12 PM, Xavier Hernandez <xhernan...@datalab.es >>> <mailto:xhernan...@datalab.es>> wrote: >>> >>>

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.11.1: Scheduled for 20th of June

On Tue, Jun 6, 2017 at 6:54 PM, Shyam wrote: > Hi, > > It's time to prepare the 3.11.1 release, which falls on the 20th of > each month [4], and hence would be June-20th-2017 this time around. > > This mail is to call out the following, > > 1) Are there any pending *blocker*

Re: [Gluster-devel] geo-rep regression because of node-uuid change

sting >> node-uuid xattr will not return that UUID if a node is down. What is the >> behavior with the proposed xattr? >> >> Let me know your thoughts. >> >> regards >> Aravinda VK >> >> On 06/20/2017 03:06 PM, Aravinda wrote: >> &

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.11.1: Scheduled for 20th of June

On Tue, Jun 20, 2017 at 7:37 PM, Shyam wrote: > Hi, > > Release tagging has been postponed by a day to accommodate a fix for a > regression that has been introduced between 3.11.0 and 3.11.1 (see [1] for > details). > > As a result 3.11.1 will be tagged on the 21st June as

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.11.1: Scheduled for 20th of June

On Wed, Jun 21, 2017 at 9:12 PM, Shyam <srang...@redhat.com> wrote: > On 06/21/2017 11:37 AM, Pranith Kumar Karampuri wrote: > >> >> >> On Tue, Jun 20, 2017 at 7:37 PM, Shyam <srang...@redhat.com >> <mailto:srang...@redhat.com>> wrote: >> &

[Gluster-devel] reagarding backport information while porting patches

Smoke: Gluster Build System <jenk...@build.gluster.org> > Reviewed-by: Pranith Kumar Karampuri <pkara...@redhat.com> > Tested-by: Pranith Kumar Karampuri <pkara...@redhat.com> > NetBSD-regression: NetBSD Build System <jenk...@build.gluster.org> > Rev

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 9:37 AM, Ravishankar N <ravishan...@redhat.com> wrote: > On 06/23/2017 09:15 AM, Pranith Kumar Karampuri wrote: > > hi, > Now that we are doing backports with same Change-Id, we can find the > patches and their backports both online and in the t

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 1:30 PM, Niels de Vos <nde...@redhat.com> wrote: > On Fri, Jun 23, 2017 at 09:15:21AM +0530, Pranith Kumar Karampuri wrote: > > hi, > > Now that we are doing backports with same Change-Id, we can find the > > patches and their backports

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 4:21 PM, Niels de Vos <nde...@redhat.com> wrote: > On Fri, Jun 23, 2017 at 03:53:42PM +0530, Pranith Kumar Karampuri wrote: > > On Fri, Jun 23, 2017 at 3:01 PM, Niels de Vos <nde...@redhat.com> wrote: > > > > > On Fri, Jun 23, 201

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 7:06 PM, Shyam <srang...@redhat.com> wrote: > On 06/23/2017 07:00 AM, Pranith Kumar Karampuri wrote: > >> Note that all of this is just my opinion, and based on working with >> many >> different projects that use git (or ot

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 7:24 PM, Shyam <srang...@redhat.com> wrote: > On 06/23/2017 09:48 AM, Pranith Kumar Karampuri wrote: > >> >> >> On Fri, Jun 23, 2017 at 7:06 PM, Shyam <srang...@redhat.com >> <mailto:srang...@redhat.com>> wrote: >>

Re: [Gluster-devel] Just a thought, a better way to rebuild replica when some bricks go down rather than replace-brick

On Thu, May 25, 2017 at 11:35 AM, Jaden Liang wrote: > Hi all, > > As I know, glusterfs have to replace brick to rebuild replica when some > bricks go down. In most commercial distributed storage system, there is a > key spec that indicates how fast to rebuild data when

Re: [Gluster-devel] [Gluster-users] Fwd: Re: GlusterFS removal from Openstack Cinder

On Wed, May 24, 2017 at 9:10 PM, Joe Julian wrote: > Forwarded for posterity and follow-up. > > Forwarded Message > Subject: Re: GlusterFS removal from Openstack Cinder > Date: Fri, 05 May 2017 21:07:27 + > From: Amye Scavarda

Re: [Gluster-devel] Release 3.11: Blocker bugs status

Yes, Sunil also wrote a script which does rebalance with the patch successfully. I went ahead and closed it as duplicate. On Fri, May 26, 2017 at 3:04 AM, Shyam wrote: > Hi, > > All marked blockers against 3.11 have been fixed, except this one, > > Bug:

Re: [Gluster-devel] Release 3.11: Release notes updates!!! (1 day remaining)

On Fri, May 26, 2017 at 2:53 AM, Shyam wrote: > Hi, > > If your name is on the following list, we need your help in updating the > release notes and thus closing out the final stages of 3.11 release. Please > do the needful by end of this week! (which means there is single

Re: [Gluster-devel] [Gluster-Maintainers] Backport for "Add back socket for polling of events immediately..."

On Mon, May 29, 2017 at 8:46 AM, Raghavendra G wrote: > Replying to all queries here: > > * Is it a bug or performance enhancement? > Its a performance enhancement. No functionality is broken if this patch > is not taken in. > > * Are there performance numbers to

Re: [Gluster-devel] threads on client side xlator (EC)

On Thu, Jun 1, 2017 at 3:18 PM, jayakrishnan mm wrote: > Hi, > Assuming a client side xlator,(e.g, EC) how are write requests (to same > file) from upper layer (DHT)are handled ? Each time ec_gf_writev() is > processed by the same thread ? > Not necessarily. It

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

On Mon, Jun 5, 2017 at 12:40 PM, Xie Changlong <xiechanglon...@gmail.com> wrote: > 在 6/5/2017 2:34 PM, Pranith Kumar Karampuri 写道: > >> What is your usecase if I may ask? >> >> > Only fio/iozone now, maybe you can give me better test sugguestion :) > I mean

Re: [Gluster-devel] Adding one variable to inode structure

tfattr after every create, > for video files. Am I correct? > How consistent should it be? May be you can do this operation on another thread or something in the background so that your application may not see the delay in doing I/O? > > On Mon, Jun 5, 2017 at 11:28 AM, Pranith Kumar Kar

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

On Tue, Jun 6, 2017 at 8:14 AM, Xie Changlong <xiechanglon...@gmail.com> wrote: > 在 6/5/2017 6:30 PM, Pranith Kumar Karampuri 写道: > >> I meant what are you using gluster for? VM workload or image/video file >> creation or lots of small files etc etc. >> > > 1)

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

On Wed, Jun 7, 2017 at 2:28 PM, Xie Changlong <xiechanglon...@gmail.com> wrote: > 在 6/7/2017 4:47 PM, Pranith Kumar Karampuri 写道: > >> Yes, they do. The patches I gave earlier provide the facility to this in >> io-stats. Do let us know if you have any doubts. >>

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

On Wed, Jun 7, 2017 at 1:55 PM, Xie Changlong <xiechanglon...@gmail.com> wrote: > 在 6/7/2017 3:08 PM, Pranith Kumar Karampuri 写道: > >> On Tue, Jun 6, 2017 at 8:14 AM, Xie Changlong <xiechanglon...@gmail.com> >> wrote: >> >> 在 6/5/2017 6:30 PM, Pranit

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

I don't know enough about this. Vijay has idea about this, so will respond later. > > Yuan > -- > > > *From:* Pranith Kumar Karampuri <pkara...@redhat.com> > *Date:* 2017-06-07 15:38 > *To:* Xie Changlong <xiechanglon.

[Gluster-devel] Making efficient use of conditional variables

hi, I just read the pdf linked in the patch https://review.gluster.org/16832 and learned something I didn't know before about how to use conditional variables efficiently. Just wanted to share it here in case it is useful for others too. Do go through the patch as well to see how the idea is

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

What is your usecase if I may ask? On Mon, Jun 5, 2017 at 11:08 AM, Xie Changlong <xiechanglon...@gmail.com> wrote: > 在 6/5/2017 1:22 PM, Pranith Kumar Karampuri 写道: > >> On Mon, Jun 5, 2017 at 8:29 AM, Xie Changlong <xiechanglon...@gmail.com> >> wrote: >> &

Re: [Gluster-devel] Adding one variable to inode structure

ch xlator do you want this information? Or do you want this on mount? > > On Mon, Jun 5, 2017 at 10:00 AM, Pranith Kumar Karampuri < > pkara...@redhat.com> wrote: > >> >> >> On Mon, Jun 5, 2017 at 9:55 AM, Tahereh Fattahi <t28.fatt...@gmail.com> >> wrote: >>

Re: [Gluster-devel] Adding one variable to inode structure

it will automatically heal this extended attribute etc. On Mon, Jun 5, 2017 at 12:10 PM, Tahereh Fattahi <t28.fatt...@gmail.com> wrote: > I want in in mount directory in client side > > On Mon, Jun 5, 2017 at 11:07 AM, Pranith Kumar Karampuri < > pkara...@redhat.com> wrote: > &

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

On Mon, Jun 5, 2017 at 8:29 AM, Xie Changlong <xiechanglon...@gmail.com> wrote: > 在 6/5/2017 10:50 AM, Pranith Kumar Karampuri 写道: > >> I think there have been improvements here to use special instructions to >> > > if "special instructions" means profi

Re: [Gluster-devel] Adding one variable to inode structure

This sounds hacky. In general anything that is specific about an inode, we try to store it in inode-ctx. Who uses this information about presence of video-file and how? May be with that knowledge there could be a possibility we can improve the solution. Do let us know the complete problem you are

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

I think there have been improvements here to use special instructions to do the increments instead of taking spin-locks and doing increments. So may be it doesn't affect performance as much anymore. I think if you don't see a difference, then the enhancements are doing a good job :-). Which

Re: [Gluster-devel] Adding one variable to inode structure

unlink to make sure you get the functionality you want. Basically this xlator helps you in indexing a behavior. We use this for indexing directories/files that need heal etc. > > On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri < > pkara...@redhat.com> wrote: > >> This sound

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.11: Has been Branched (and pending feature notes)

On Wed, May 3, 2017 at 2:36 PM, Kaushal M <kshlms...@gmail.com> wrote: > On Tue, May 2, 2017 at 3:55 PM, Pranith Kumar Karampuri > <pkara...@redhat.com> wrote: > > > > > > On Sun, Apr 30, 2017 at 9:01 PM, Shyam <srang...@redhat.com> wrote: > >> &

Re: [Gluster-devel] [Gluster-users] [DHT] The myth of two hops for linkto file resolution

On Sun, Apr 30, 2017 at 9:33 AM, Raghavendra Gowdappa wrote: > All, > > Its a common perception that the resolution of a file having linkto file > on the hashed-subvol requires two hops: > > 1. client to hashed-subvol. > 2. client to the subvol where file actually resides. >

Re: [Gluster-devel] Enabling shard on EC

It is never been tested. That said, I don't see any missing pieces that we know of for it to work. Please note that sharding works only for single writer cases at the moment. Do let us know if you find any problems and we will fix them. On Wed, May 3, 2017 at 2:17 PM, Ankireddypalle Reddy

Re: [Gluster-devel] Enabling shard on EC

d to any kind of data inconsistencies. > We only tested it for single writer cases such as VM usecases. We need to bring in transaction framework for sharding to work with multiple writers. > > > Thanks and Regards, > > Ram > > *From:* Pranith Kumar Karampuri [mailto:pkara...

Re: [Gluster-devel] Don't allow data loss via add-brick (was Re: [Gluster-users] Add single server)

Yeah it is a good idea. I asked him to raise a bug and we can move forward with it. On Mon, May 1, 2017 at 9:07 PM, Joe Julian wrote: > > On 04/30/2017 01:13 AM, lemonni...@ulrar.net wrote: > >> So I was a little but luck. If I has all the hardware part, probably i >>>

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.11: Has been Branched (and pending feature notes)

On Sun, Apr 30, 2017 at 9:01 PM, Shyam wrote: > Hi, > > Release 3.11 for gluster has been branched [1] and tagged [2]. > > We have ~4weeks to release of 3.11, and a week to backport features that > slipped the branching date (May-5th). > > A tracker BZ [3] has been opened

Re: [Gluster-devel] [Gluster-users] Don't allow data loss via add-brick (was Re: Add single server)

On Tue, May 2, 2017 at 9:16 AM, Pranith Kumar Karampuri <pkara...@redhat.com > wrote: > Yeah it is a good idea. I asked him to raise a bug and we can move forward > with it. > +Raghavendra/Nitya who can help with the fix. > > On Mon, May 1, 2017 at 9:07 PM, Joe Julian &

Re: [Gluster-devel] Enabling shard on EC

gt; > Thanks and Regards, > > Ram > > *From:* Pranith Kumar Karampuri [mailto:pkara...@redhat.com] > *Sent:* Thursday, May 04, 2017 6:17 AM > > *To:* Ankireddypalle Reddy > *Cc:* Gluster Devel (gluster-devel@gluster.org); gluster-us...@gluster.org > *Subject:* Re: [Glus

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.11: Has been Branched (and pending feature notes)

ote: > > On Thu, May 4, 2017 at 4:38 PM, Niels de Vos <nde...@redhat.com> wrote: > >> On Thu, May 04, 2017 at 03:39:58PM +0530, Pranith Kumar Karampuri wrote: > >>> On Wed, May 3, 2017 at 2:36 PM, Kaushal M <kshlms...@gmail.com> wrote: > >>&g

Re: [Gluster-devel] tests/basic/pump.t - what is it used for?

It was used for testing pump xlator functionality. When replace-brick is done on a distribute volume, it would lead to pump xlator migrating data to the destination brick from source. I guess we can delete this test. I don't think we support pump xlator anymore. On Fri, Sep 8, 2017 at 10:02 AM,

Re: [Gluster-devel] Need help figuring out the reason for test failure

hanks for the pointer. Able to get the logs now! > > On Tue, Nov 28, 2017 at 8:06 AM, Pranith Kumar Karampuri < > pkara...@redhat.com> wrote: > >> One of my patches(https://review.gluster.org/18857) is consistently >> leading to a failure for the test: >> >> tes

[Gluster-devel] Need help figuring out the reason for test failure

One of my patches(https://review.gluster.org/18857) is consistently leading to a failure for the test: tests/bugs/core/bug-1432542-mpx-restart-crash.t https://build.gluster.org/job/centos6-regression/7676/consoleFull Jeff/Atin, Do you know anything about these kinds of failures for this

[Gluster-devel] reflink support for glusterfs and gluster-block using it for taking snapshots

hi, I just created a github issue for reflink support (#349) in glusterfs. We are intending to use this feature to do block snapshots in gluster-block. Please let us know your comments on the github issue. I have added the changes we may need

[Gluster-devel] Thin-arbiter design to solve stretch cluster usecase

hi, I created a new issue which shares a link of design document for this feature. Please add comments to the design document itself rather than github issue, so that all comments are in one place. Thanks in advance. -- Pranith

Re: [Gluster-devel] Tie-breaker logic for blocking inodelks/entrylks

:56 AM, Pranith Kumar Karampuri <pkara...@redhat.com > wrote: > This github issue <https://github.com/gluster/glusterfs/issues/354> talks > about the logic for implementing tie-breaker logic for blocking > inodelks/entrylks. Your comments are welcome on the issue. > > --

[Gluster-devel] Tie-breaker logic for blocking inodelks/entrylks

This github issue talks about the logic for implementing tie-breaker logic for blocking inodelks/entrylks. Your comments are welcome on the issue. -- Pranith ___ Gluster-devel mailing list

Re: [Gluster-devel] reflink support for glusterfs and gluster-block using it for taking snapshots

On Tue, Nov 7, 2017 at 5:16 PM, Niels de Vos <nde...@redhat.com> wrote: > On Tue, Nov 07, 2017 at 07:43:17AM +0530, Pranith Kumar Karampuri wrote: > > hi, > > I just created a github issue for reflink support > > <https://github.com/gluster/glusterfs/issu

Re: [Gluster-devel] reflink support for glusterfs and gluster-block using it for taking snapshots

On Thu, Nov 9, 2017 at 8:26 PM, Niels de Vos <nde...@redhat.com> wrote: > On Tue, Nov 07, 2017 at 05:59:32PM +0530, Pranith Kumar Karampuri wrote: > > On Tue, Nov 7, 2017 at 5:16 PM, Niels de Vos <nde...@redhat.com> wrote: > > > > > On Tue, Nov 07, 201

<    2   3   4   5   6   7   8   >