Re: [Gluster-devel] Build up of xfsmount dirs... ;)
Hi Vijay, Can you please take this patch in? http://review.gluster.org/#/c/8138/ Thanks & Regads, Rajesh - Original Message - > From: "Justin Clift" > To: "Rajesh Joseph" > Cc: "Gluster Devel" > Sent: Friday, June 20, 2014 7:49:57 PM > Subject: Re: Build up of xfsmount dirs... ;) > > No worries. :) > > + Justin > > > On 20/06/2014, at 2:59 PM, Rajesh Joseph wrote: > > Thanks Justin for letting me know. Its clearly a bug in the implementation. > > I will send a patch to fix this. Meanwhile if it is causing any test > > failures or other issues then you can have a temporary fix to delete them > > in the script. > > > > Thanks & Regards, > > Rajesh > > > > - Original Message - > >> From: "Justin Clift" > >> To: "Rajesh Joseph" > >> Cc: "Gluster Devel" > >> Sent: Friday, June 20, 2014 7:07:06 PM > >> Subject: Build up of xfsmount dirs... ;) > >> > >> Hi Rajesh, > >> > >> Looking at the regression testing boxes this morning, they all have > >> several thousand /tmp/xfsmount* dirs on them. > >> > >> Seems like they're coming from this: > >> > >> f1705e2d (Rajesh Joseph 2014-06-05 10:00:33 +0530 3988) char > >> template [] = "/tmp/xfsmountXX"; > >> > >> (it's the only mention in the source for /tmp/xfsmount...) > >> > >> Could it be the case that the directory gets made, but never > >> gets cleaned up? If so, is there a feasible way to clean it > >> up after use? > >> > >> We *can* just change the regression test scripting to nuke > >> /tmp/xfsmount* after each run. But wondering it's something > >> Gluster should take care of itself. :) > >> > >> Regards and best wishes, > >> > >> Justin Clift > >> > >> -- > >> GlusterFS - http://www.gluster.org > >> > >> An open source, distributed file system scaling to several > >> petabytes, and handling thousands of clients. > >> > >> My personal twitter: twitter.com/realjustinclift > >> > >> > > -- > GlusterFS - http://www.gluster.org > > An open source, distributed file system scaling to several > petabytes, and handling thousands of clients. > > My personal twitter: twitter.com/realjustinclift > > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Build up of xfsmount dirs... ;)
No worries. :) + Justin On 20/06/2014, at 2:59 PM, Rajesh Joseph wrote: > Thanks Justin for letting me know. Its clearly a bug in the implementation. I > will send a patch to fix this. Meanwhile if it is causing any test failures > or other issues then you can have a temporary fix to delete them in the > script. > > Thanks & Regards, > Rajesh > > - Original Message - >> From: "Justin Clift" >> To: "Rajesh Joseph" >> Cc: "Gluster Devel" >> Sent: Friday, June 20, 2014 7:07:06 PM >> Subject: Build up of xfsmount dirs... ;) >> >> Hi Rajesh, >> >> Looking at the regression testing boxes this morning, they all have >> several thousand /tmp/xfsmount* dirs on them. >> >> Seems like they're coming from this: >> >> f1705e2d (Rajesh Joseph 2014-06-05 10:00:33 +0530 3988) char >> template [] = "/tmp/xfsmountXX"; >> >> (it's the only mention in the source for /tmp/xfsmount...) >> >> Could it be the case that the directory gets made, but never >> gets cleaned up? If so, is there a feasible way to clean it >> up after use? >> >> We *can* just change the regression test scripting to nuke >> /tmp/xfsmount* after each run. But wondering it's something >> Gluster should take care of itself. :) >> >> Regards and best wishes, >> >> Justin Clift >> >> -- >> GlusterFS - http://www.gluster.org >> >> An open source, distributed file system scaling to several >> petabytes, and handling thousands of clients. >> >> My personal twitter: twitter.com/realjustinclift >> >> -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Build up of xfsmount dirs... ;)
Thanks Justin for letting me know. Its clearly a bug in the implementation. I will send a patch to fix this. Meanwhile if it is causing any test failures or other issues then you can have a temporary fix to delete them in the script. Thanks & Regards, Rajesh - Original Message - > From: "Justin Clift" > To: "Rajesh Joseph" > Cc: "Gluster Devel" > Sent: Friday, June 20, 2014 7:07:06 PM > Subject: Build up of xfsmount dirs... ;) > > Hi Rajesh, > > Looking at the regression testing boxes this morning, they all have > several thousand /tmp/xfsmount* dirs on them. > > Seems like they're coming from this: > > f1705e2d (Rajesh Joseph 2014-06-05 10:00:33 +0530 3988) char > template [] = "/tmp/xfsmountXX"; > > (it's the only mention in the source for /tmp/xfsmount...) > > Could it be the case that the directory gets made, but never > gets cleaned up? If so, is there a feasible way to clean it > up after use? > > We *can* just change the regression test scripting to nuke > /tmp/xfsmount* after each run. But wondering it's something > Gluster should take care of itself. :) > > Regards and best wishes, > > Justin Clift > > -- > GlusterFS - http://www.gluster.org > > An open source, distributed file system scaling to several > petabytes, and handling thousands of clients. > > My personal twitter: twitter.com/realjustinclift > > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Build up of xfsmount dirs... ;)
Hi Rajesh, Looking at the regression testing boxes this morning, they all have several thousand /tmp/xfsmount* dirs on them. Seems like they're coming from this: f1705e2d (Rajesh Joseph 2014-06-05 10:00:33 +0530 3988) char template [] = "/tmp/xfsmountXX"; (it's the only mention in the source for /tmp/xfsmount...) Could it be the case that the directory gets made, but never gets cleaned up? If so, is there a feasible way to clean it up after use? We *can* just change the regression test scripting to nuke /tmp/xfsmount* after each run. But wondering it's something Gluster should take care of itself. :) Regards and best wishes, Justin Clift -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
