rick
> The system on which you are getting the errors, is it a vm which I can
> access? So that I can try few more extra tests?
>
>
> > - Original Message -
> > From: "Rick Macklem" <rmack...@uoguelph.ca>
> > To: "Sakshi Bansal" &l
> > Sorry this isn't particularily useful, but it's all I have, rick
> > The system on which you are getting the errors, is it a vm which I can
> > access? So that I can try few more extra tests?
> >
> >
> > > - Original Message -
> > >
- Original Message -
> From: "Rick Macklem" <rmack...@uoguelph.ca>
> To: "Sakshi Bansal" <saban...@redhat.com>
> Cc: "Raghavendra Gowdappa" <rgowd...@redhat.com>, "Gluster Devel"
> <gluster-devel@gluster.org>
> Sent:
age -
> From: "Rick Macklem" <rmack...@uoguelph.ca>
> To: "Sakshi Bansal" <saban...@redhat.com>
> Cc: "Raghavendra Gowdappa" <rgowd...@redhat.com>, "Gluster Devel"
> <gluster-devel@gluster.org>
> Sent: Thursday, Jan
Sakshi Bansal wrote:
> The directory deletion is failing with ENOTEMPTY since not all the files
> inside it have been deleted. Looks like lookup is not listing all the files.
> It is possible that cluster.lookup-optimize could be the culprit here. When
> did you turn this option 'on'? Was it
org>
Sent: Thursday, January 21, 2016 10:03:37 AM
Subject: Re: [Gluster-devel] rm -r problem on FreeBSD port
Sakshi Bansal wrote:
> The directory deletion is failing with ENOTEMPTY since not all the files
> inside it have been deleted. Looks like lookup is not listing all the files.
&
Sakshi Bansai wrote:
> Hi Rick,
>
> Could you get us some more information about your setup:
>
First off, just to make it clear, the setup is a simple 2 brick distribute
(no replication or ...) like the doc recommends for a quick tryout.
> 1) Are you parallely doing 'rm -r' from multiple mount
- Original Message -
From: "Sakshi Bansal" <saban...@redhat.com>
To: "Rick Macklem" <rmack...@uoguelph.ca>
Cc: "rhs-zteam" <rhs-zt...@redhat.com>
Sent: Wednesday, January 20, 2016 11:34:17 AM
Subject: Re: [Gluster-devel] rm -r probl
> Sometimes. When this occurs (I get something like this every time I do an "rm
> -r")
> I can sometimes go into the directory and do an explicit "rm ". At that
> point
> it will report that the file doesn't exist (I suspect because it sees 2 of
> them and
> the second one is gone once the
Sakshi Bansal wrote:
>
> > Sometimes. When this occurs (I get something like this every time I do an
> > "rm -r")
> > I can sometimes go into the directory and do an explicit "rm ". At
> > that point
> > it will report that the file doesn't exist (I suspect because it sees 2 of
> > them and
> >
The directory deletion is failing with ENOTEMPTY since not all the files inside
it have been deleted. Looks like lookup is not listing all the files.
It is possible that cluster.lookup-optimize could be the culprit here. When did
you turn this option 'on'? Was it during the untaring of the
On 01/18/2016 06:18 PM, Rick Macklem wrote:
Hi,
I have a simple gluster volume made up of 2 bricks using
distribute (running on the FreeBSD port of 3.7.6).
When I do a "rm -rf " for a fairly large tree, I
sometimes get "Directory not empty" errors.
When I look in the directory (even after an
- Original Message -
> From: "Rick Macklem"
> To: "Gluster Devel"
> Sent: Tuesday, January 19, 2016 4:48:21 AM
> Subject: [Gluster-devel] rm -r problem on FreeBSD port
>
> Hi,
>
> I have a simple gluster volume made up of 2 bricks
Hi Rick,
Could you get us some more information about your setup:
1) Are you parallely doing 'rm -r' from multiple mount points? Or are you doing
'ls' while rm was in progress?
2) Is the error just a one time occurrence or do you still see it when you try
and remove the directory?
3) The
14 matches
Mail list logo