From 1e289290e6b940d50df639b1fd330c2295c059ca Mon Sep 17 00:00:00 2001 From: linggao Date: Tue, 24 May 2011 20:50:45 +0000 Subject: [PATCH] added how to handle statelite for snmove man page git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@9677 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd --- xCAT-client/pods/man1/snmove.1.pod | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/xCAT-client/pods/man1/snmove.1.pod b/xCAT-client/pods/man1/snmove.1.pod index de01795dc..3428b8c2d 100644 --- a/xCAT-client/pods/man1/snmove.1.pod +++ b/xCAT-client/pods/man1/snmove.1.pod @@ -77,6 +77,10 @@ Note: You can also run other postscripts useing -P option if needed. When the B command is executed the new service node must be running but the original service node may be down. +Note: On a Linux cluster, for NFS statelite nodes that do not use external NFS server, if the original service node is down, the nodes it manages will be down too. You must run nodeset command and then reboot the nodes after running snmove. For stateless nodes and RAMDisk statelite nodes, the nodes will be up even if the original service node is down. However, make sure to run nodeset command if you decide to reboot the nodes later. + +Note: For statelite nodes, + =head1 OPTIONS =over 10