- Original Message -
From: "Atin Mukherjee"
To: "Poornima Gurusiddaiah" , "Avra Sengupta"
, "Sakshi Bansal"
Cc: "Gluster Devel" , "Kotresh Hiremath Ravishankar"
, "Rajesh Joseph" , "Ravishankar N"
, &
Hi,
We need some more information regarding the test case:
1) Are you parallely running rm -rf or an rm -rf and ls from multiple mount
points?
2) On the bricks do you see the directories holding files or directories?
- Original Message -
From: "Deng ShaoHui"
To: gluster-devel@gluster.or
Regarding the ENOTEMPTY error I need some more information:
1) Are there multiple clients running the same script or performing rmdir on
the directory that complained?
2) Was there a rebalance running when you saw the error?
3) Before you ran the second rmdir that successfully removed the director
http://review.gluster.org/#/c/13544/
- Original Message -
From: "Prasanna Kumar Kalever"
To: "Sakshi Bansal"
Cc: "Gluster Devel"
Sent: Wednesday, March 16, 2016 5:44:54 PM
Subject: Re: [Gluster-devel] regression failures in bug-860663.t
Can you pas
There is a fix for the test case that went after this regression failure. I
suppose a rebase should fix the issue.
- Original Message -
From: "Prasanna Kumar Kalever"
To: "Sakshi Bansal"
Cc: "Gluster Devel"
Sent: Wednesday, March 16, 2016 3:14:35
Hi,
Can you send any one patch for which you saw the failure.
- Original Message -
From: "Prasanna Kumar Kalever"
To: "Gluster Devel"
Sent: Wednesday, March 16, 2016 2:54:45 PM
Subject: [Gluster-devel] regression failures in bug-860663.t
Hi,
Noticed too many regression failures in
./
Hi,
Patch http://review.gluster.org/#/c/10906/ (recently merged) fixes
./tests/bugs/distribute/bug-860663.t.
- Original Message -
From: "Xavier Hernandez"
To: "Poornima Gurusiddaiah" , "Gluster Devel"
, "Manikandan Selvaganesan" ,
"Susant Palai" , "Nithya Balachandran"
Sent: Tuesday
Hi Willy,
Its great to see your interest in GlusterFS. But due to some changes in the
lookup related area the current lookup-optimize design does not hold good. Do
you have any other areas in GlusterFS that you would like to work on. Please
let us know so that we can help you further.
- Or
Just checking if the changes made to brick_up_status by patch #12913 are
required in 3.7 as well (since it is not backported)
- Original Message -
From: "Ravishankar N"
To: "Venky Shankar" , "Sakshi Bansal"
Cc: "Ravishankar Narayanankutty" , &quo
> If anything is going in mainline I'd encourage the same to be backported
> irrespective of the severity of the fix, so that's out of the equation.
Will keep this is mind in future.
> I'd like to stick to remove brick_up_status(). Please use the same in
> all the places. You can include all the
yscall failed when the rm on a file
>fails. Also can you share the ktrace
log files if you have them?
> 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 ex
Hi,
I suppose someone from glusterd team can confirm if the patch #10954 requires a
backport to 3.7.
Even if a backport is required it would probably be better to first remove
brick_up_status() and use just brick_up_status_1()
or vice versa (to avoid any further confusion on which function to u
it the
unlink that is failing.
- Original Message -
From: "Rick Macklem"
To: "Sakshi Bansal"
Cc: "Raghavendra Gowdappa" , "Gluster Devel"
Sent: Thursday, January 21, 2016 10:03:37 AM
Subject: Re: [Gluster-devel] rm -r problem on FreeBSD po
- Original Message -
From: "Sakshi Bansal"
To: "Rick Macklem"
Cc: "rhs-zteam"
Sent: Wednesday, January 20, 2016 11:34:17 AM
Subject: Re: [Gluster-devel] rm -r problem on FreeBSD port
Another info that would help is an strace when the rm fails to remove
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 source
> 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 firs
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 direct
The crash seems to happen in the function glusterfs_rebalance_event_notify_cbk
since the frame is corrupted. I guess frame got corrupted
since the calling function glusterfs_rebalance_event_notify seems to
immediately call STACK_DESTROY after calling the cbk.
I ran the snapshot test to check,
The above link may not be accessible to all. In that case please refer to this:
https://public.pad.fsfe.org/p/dht_lookup_optimize
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
Hi,
Design for making lookup-optimize on by default, please provide your feedback.
http://pad.engineering.redhat.com/dht-lookup-optimize
--
Thanks and Regards
Sakshi Bansal
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http
20 matches
Mail list logo
