Re: [Gluster-devel] file version on glusterfs using libgit

2013-03-08 Thread Luis Pabon
This sounds really interesting, but I do have some questions about Git (or any SCM) as a solution for file version support. 1. How well does Git handle large binary files like VM images? Does it keep a copy for each one, or does it keep diffs? 2. Does Git, or another SCM, allow for the deleti

Re: [Gluster-devel] Quota command failed (with 3.4 alpa 2)

2013-03-08 Thread Vijay Bellur
On 03/08/2013 09:07 PM, Nux! wrote: On 08.03.2013 15:31, Vijay Bellur wrote: Can you please provide the o/p of: gluster system:: fsm log Do you have any firewall rules on the nodes of the cluster? Connection refused errors seem to indicate so. Hello, I've got all traffic between peers ac

[Gluster-devel] Semi-OT: review.gluster.org no longer working with FAS accounts

2013-03-08 Thread Justin Clift
Hi guys, It looks like the Fedora Account System people have switched around the OpenID endpoint. So, trying to log in to review.gluster.org with Fedora OpenID using this format no longer works: https://admin.fedoraproject.org/accounts/openid/id/USERNAME The new OpenID endpoint format is now:

Re: [Gluster-devel] Quota command failed (with 3.4 alpa 2)

2013-03-08 Thread Nux!
On 08.03.2013 15:31, Vijay Bellur wrote: Can you please provide the o/p of: gluster system:: fsm log Do you have any firewall rules on the nodes of the cluster? Connection refused errors seem to indicate so. Hello, I've got all traffic between peers accepted so I don't think it's that. P

Re: [Gluster-devel] Quota command failed (with 3.4 alpa 2)

2013-03-08 Thread Vijay Bellur
On 03/08/2013 08:45 PM, Nux! wrote: Hello, After the recent upgrade to 3.4 alpha 2 blew up in my face, I started from scratch, removing all packages, deleting /var/lib/gluster* and formatting the bricks partition. First problem: Enabling quota on a new empty volume fails: [root@2216 ~]# gluste

[Gluster-devel] Quota command failed (with 3.4 alpa 2)

2013-03-08 Thread Nux!
Hello, After the recent upgrade to 3.4 alpha 2 blew up in my face, I started from scratch, removing all packages, deleting /var/lib/gluster* and formatting the bricks partition. First problem: Enabling quota on a new empty volume fails: [root@2216 ~]# gluster volume quota internalad enable Q

Re: [Gluster-devel] file version on glusterfs using libgit

2013-03-08 Thread Niels de Vos
On Fri, Mar 08, 2013 at 06:00:24AM -0500, Shishir Gowda wrote: > Hi Niels, > > Thinking out aloud, I think the snaps(in file version context) can be > displayed as branches (list). Well, I am not sure if branches are really needed. Isn't linear history sufficient? Every change should be committ

Re: [Gluster-devel] file version on glusterfs using libgit

2013-03-08 Thread Shishir Gowda
Hi Niels, Thinking out aloud, I think the snaps(in file version context) can be displayed as branches (list). Once the user cd's into any one of them, we could do a git checkout of the branch. That should mimic the behaviour. With regards, Shishir - Original Message - From: "Shishir

Re: [Gluster-devel] file version on glusterfs using libgit

2013-03-08 Thread Shishir Gowda
Hi Niels, My inclination too is to load git ontop of posix xlator. I was thinking of making previous versions (based on some policy) to be treated a new branch. We could see how to export these branches as user visible dirs. With regards, Shishir - Original Message - From: "Niels de V

Re: [Gluster-devel] file version on glusterfs using libgit

2013-03-08 Thread Niels de Vos
On Thu, Mar 07, 2013 at 12:54:41AM -0500, Shishir Gowda wrote: > Hi All, > > Was playing around with git on glusterfs volume, to provide was of file > version support. > > And initial run is encouraging. > > A brief overview what was tried: > > Approach 1: Glusterfs volume as a git repo > > 1

Re: [Gluster-devel] [PATCH] [master] glusterd: fix segfault on volume status detail

2013-03-08 Thread Lars Ellenberg
On Wed, Mar 06, 2013 at 12:19:14PM +0100, Lars Ellenberg wrote: > From: Lars Ellenberg > > If for some reason glusterd_get_brick_root() fails, > it frees the gf_strdup'ed *mount_point in its own error path, > and returns -1. > > Unfortunately it already had assigned that pointer value > to the o