[Gluster-devel] glusterfs-3.3.0qa34 released

[Ian Latter]

Hello,


  I've written a work around for this issue (in 3.3.0qa35) 
by adding a new configuration option to glusterd 
(ignore-strict-checks) but there are additional checks 
within the posix brick/xlator.  I can see that volume starts 
but the bricks inside it fail shortly there-after, and that of 
the 5 disks in my volume three of them have one 
volume_id and two them have another - so this isn't going 
to be resolved without some human intervention.

  However, while going through the posix brick/xlator I
found the "volume-id" parameter.  I've tracked it back
to the volinfo structure in the glusterd xlator.

  So before I try to code up a posix inheritance for my
glusterd work around (ignoring additional checks so
that a new volume_id is created on-the-fly / as-needed), 
does anyone know of a CLI method for passing the 
volume-id into glusterd (either via "volume create" or
"volume set")?  I don't see one from the code ...
glusterd_handle_create_volume does a uuid_generate
and its not a feature of glusterd_volopt_map ...

  Is a user defined UUID init method planned for the CLI
before 3.3.0 is released?  Is there a reason that this
shouldn't be permitted from the CLI "volume create" ?


Ta,


----- Original Message -----
>From: "Ian Latter" <ian.latter at midnightcode.org>
>To: <gluster-devel at nongnu.org>
>Subject:  Re: [Gluster-devel] glusterfs-3.3.0qa34 released
>Date: Fri, 13 Apr 2012 22:43:55 +1000
>
> 
> Hello,
> 
> 
>   Testing 3.3.0qa34, I'm seeing the same "has been 
> part of a deleted volume" error as reported;
>    
>
http://gluster.org/pipermail/gluster-users/2012-January/009533.html
>    
>
http://gluster.org/pipermail/gluster-users/2011-September/008734.html
>    
>
http://dev.gluster.com/pipermail/glusterfs/2011-July/004698.html
> 
> 
>   My mount points are created dynamically in a 
> stateless memory file system on each boot, so I'm
> not seeing this carried over from the previous boot
> via the mount point; the extended attributes are 
> able to be listed but their values can't be retrieved 
> and I can't delete them (attr version 2.4.46).
> 
>   Is there a work-around or solution to this (without
> re-formatting the storage device/s)?
> 
> 
> Thanks,
> 
> 
> 
> ----- Original Message -----
> >From: "John Mark Walker" <johnmark at redhat.com>
> >To: "gluster-users" <gluster-users at gluster.org>
> >Subject:  Re: [Gluster-devel] glusterfs-3.3.0qa34 released
> >Date: Tue, 10 Apr 2012 14:16:52 -0400
> >
> > Hey guys - please test this. This QA release is slated to
> become beta3.
> > 
> > -JM
> > 
> > 
> > ----- Original Message -----
> > > 
> > > http://bits.gluster.com/pub/gluster/glusterfs/3.3.0qa34/
> > > 
> > >
>
http://bits.gluster.com/pub/gluster/glusterfs/src/glusterfs-3.3.0qa34.tar.gz
> > > 
> > > This release is made off v3.3.0qa34
> > > 
> > > -- /home/vijay/bin/bits-release on build.gluster.com
> > > 
> > > _______________________________________________
> > > Gluster-devel mailing list
> > > Gluster-devel at nongnu.org
> > > https://lists.nongnu.org/mailman/listinfo/gluster-devel
> > > 
> > 
> > _______________________________________________
> > Gluster-devel mailing list
> > Gluster-devel at nongnu.org
> > https://lists.nongnu.org/mailman/listinfo/gluster-devel
> > 
> 
> 
> --
> Ian Latter
> Late night coder ..
> http://midnightcode.org/
> 
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> https://lists.nongnu.org/mailman/listinfo/gluster-devel
> 


--
Ian Latter
Late night coder ..
http://midnightcode.org/