Gluster users - Apr 2015 - Disastrous performance with rsync to mounted Gluster volume.

On 04/23/2015 04:41 PM, Ernie Dunbar wrote:
> On 2015-04-23 12:58, Ben Turner wrote:
>
>>
>> +1, lets nuke everything and start from a known good.  Those error
>> messages make me think something is really wrong with how we are
>> copying the data.  Gluster does NFS by default so you shouldn't
have
>> have to reconfigure anything after you recreate the volume.
>>
>
> Okay... this is a silly question. How do I do that? Deleting the 
> volume doesn't affect the files in the underlying filesystem, and I 
> get the impression that trying to delete the files in the underlying 
> filesystem without shutting down or deleting the volume would result 
> in Gluster trying to write the files back where they "belong".
>
> Should I stop the volume, delete it, then delete the files and start 
> from scratch, re-creating the volume?
That's what I would do.
>
> At this point, the cluster isn't live, so this is an entirely feasible 
> thing to do. All the data exists somewhere else already, and I just 
> need to copy it to the NFS share to get things going.
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users

----- Original Message -----
> From: "Joe Julian" <joe at julianfamily.org>
> To: gluster-users at gluster.org
> Sent: Thursday, April 23, 2015 9:10:59 PM
> Subject: Re: [Gluster-users] Disastrous performance with rsync to mounted
Gluster volume.
> 
> 
> 
> On 04/23/2015 04:41 PM, Ernie Dunbar wrote:
> > On 2015-04-23 12:58, Ben Turner wrote:
> >
> >>
> >> +1, lets nuke everything and start from a known good.  Those error
> >> messages make me think something is really wrong with how we are
> >> copying the data.  Gluster does NFS by default so you
shouldn't have
> >> have to reconfigure anything after you recreate the volume.
> >>
> >
> > Okay... this is a silly question. How do I do that? Deleting the
> > volume doesn't affect the files in the underlying filesystem, and
I
> > get the impression that trying to delete the files in the underlying
> > filesystem without shutting down or deleting the volume would result
> > in Gluster trying to write the files back where they
"belong".
> >
> > Should I stop the volume, delete it, then delete the files and start
> > from scratch, re-creating the volume?
> 
> That's what I would do.
Here is how I cleanup gluster, scroll down to the bottom it has the commands:

Look for - ** If you make a mistake or want to recreate things in a different
config here are the commands to cleanup
http://54.82.237.211/gluster-benchmark/gluster-bench-README

> 
> >
> > At this point, the cluster isn't live, so this is an entirely
feasible
> > thing to do. All the data exists somewhere else already, and I just
> > need to copy it to the NFS share to get things going.
> >
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-users
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>

On 2015-04-23 18:10, Joe Julian wrote:
> On 04/23/2015 04:41 PM, Ernie Dunbar wrote:
>> On 2015-04-23 12:58, Ben Turner wrote:
>> 
>>> 
>>> +1, lets nuke everything and start from a known good.  Those error
>>> messages make me think something is really wrong with how we are
>>> copying the data.  Gluster does NFS by default so you shouldn't
have
>>> have to reconfigure anything after you recreate the volume.
>>> 
>> 
>> Okay... this is a silly question. How do I do that? Deleting the 
>> volume doesn't affect the files in the underlying filesystem, and I
>> get the impression that trying to delete the files in the underlying 
>> filesystem without shutting down or deleting the volume would result 
>> in Gluster trying to write the files back where they
"belong".
>> 
>> Should I stop the volume, delete it, then delete the files and start 
>> from scratch, re-creating the volume?
> 
> That's what I would do.
> 
Well, apparently removing the .glusterfs directory from the brick is an 
exceptionally bad thing, and breaks gluster completely, rendering it 
inoperable. I'm going to have to post another thread about how to fix 
this mess now.