Best practice to stop the Gluster CLIENT process?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux