Thanks Joe! ...thought so! Thanks for the confirmation. Time to redesign... system was set up before my time. Oh, well... Perhaps this should be added in the manual? Or is that already in there and was overlooked? Best, Martin -----Original Message----- From: Joe Landman [mailto:landman at scalableinformatics.com] Sent: Friday, May 06, 2011 10:22 PM To: Martin Schenker Subject: Re: Best practice to stop the Gluster CLIENT process? On 05/06/2011 04:13 PM, Martin Schenker wrote: > Won't help if it's the logging process itself, I guess?!? Had that > earlier... > > Is it recommended to log somewhere else than the Gluster file system? Yes. You should log to a file system on a device that the Gluster file system is not on. > > Best, Martin > > -----Original Message----- > From: gluster-users-bounces at gluster.org > [mailto:gluster-users-bounces at gluster.org] On Behalf Of Joe Landman > Sent: Friday, May 06, 2011 9:36 PM > To: gluster-users at gluster.org > Subject: Re: Best practice to stop the Gluster CLIENT > process? > > On 05/06/2011 03:14 PM, Martin Schenker wrote: >> So if I get this right, you'll have to rip the heart out (kill all gluster >> processes; server AND client) in order to get to the local server >> filesystem. >> >> I had hoped that the client part could be left running (to the second > mirror >> brick) when doing repairs etc. Looks like a wrong assumption, I guess... > > or use fuser/lsof to determine which process is locking which volume. > Kill only that process. > > -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics Inc. email: landman at scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/sicluster phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615
