I believe the simplest way to do this is to bring your cluster down. It is possible to do this one machine at a time - leaving the cluster as a whole running, but the instructions are more difficult.
Assuming you are bringing down your cluster, do: 1. unmount gfs from all machines 2. unassemble the pool device from all machines 3. rewrite the pool labels for the pool in question from _one_ machine 4. reassemble the pool device on all machines 5. remount gfs 6. choose to add additional journals, or add space to the file system
Basically, you are forcibly growing the size of the pool (offline). Then you are making your adjustments to gfs (online).
Clearly, it is easier if the array simply makes another device available to the system - allowing an additional subpool to be added to the pool. This way, everything can be done online.
brassow
On Nov 16, 2004, at 4:50 PM, David Aquilina wrote:
On Wed, 17 Nov 2004 09:37:47 +1100, John Newbigin <jn@xxxxxxxxxxxxxx> wrote:I though pool-tool -g would do it but it seems that can only add subpools.
Is there any particular reason you don't want to add a subpool? As far as I know, adding subpools is the only way to grow a pool, and won't have any other effect than a slightly longer pool configuration file...
-- David Aquilina, RHCE dwaquilina@xxxxxxxxx
-- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster
