[gpfsug-discuss] HAWC question

Sven Oehme oehmes at gmail.com
Thu May 4 15:06:10 BST 2017


let me clarify and get back, i am not 100% sure on a cross cluster , i
think the main point was that the FS manager for that fs should be
reassigned (which could also happen via mmchmgr) and then the individual
clients that mount that fs restarted  , but i will double check and reply
later .


On Thu, May 4, 2017 at 6:39 AM Simon Thompson (IT Research Support) <
S.J.Thompson at bham.ac.uk> wrote:

> Which cluster though? The client and storage are separate clusters, so all
> the nodes on the remote cluster or storage cluster?
>
> Thanks
>
> Simon
> ________________________________________
> From: gpfsug-discuss-bounces at spectrumscale.org [
> gpfsug-discuss-bounces at spectrumscale.org] on behalf of oehmes at gmail.com [
> oehmes at gmail.com]
> Sent: 04 May 2017 14:28
> To: gpfsug main discussion list
> Subject: Re: [gpfsug-discuss] HAWC question
>
> well, it's a bit complicated which is why the message is there in the
> first place.
>
> reason is, there is no easy way to tell except by dumping the stripgroup
> on the filesystem manager and check what log group your particular node is
> assigned to and then check the size of the log group.
>
> as soon as the client node gets restarted it should in most cases pick up
> a new log group and that should be at the new size, but to be 100% sure we
> say all nodes need to be restarted.
>
> you need to also turn HAWC on as well, i assume you just left this out of
> the email , just changing log size doesn't turn it on :-)
>
> On Thu, May 4, 2017 at 6:15 AM Simon Thompson (IT Research Support) <
> S.J.Thompson at bham.ac.uk<mailto:S.J.Thompson at bham.ac.uk>> wrote:
> Hi,
>
> I have a question about HAWC, we are trying to enable this for our
> OpenStack environment, system pool is on SSD already, so we try to change
> the log file size with:
>
> mmchfs FSNAME -L 128M
>
> This says:
>
> mmchfs: Attention: You must restart the GPFS daemons before the new log
> file
> size takes effect. The GPFS daemons can be restarted one node at a time.
> When the GPFS daemon is restarted on the last node in the cluster, the new
> log size becomes effective.
>
>
> We multi-cluster the file-system, so do we have to restart every node in
> all clusters, or just in the storage cluster?
>
> And how do we tell once it has become active?
>
> Thanks
>
> Simon
>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org<http://spectrumscale.org>
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170504/af0f9a90/attachment-0002.htm>


More information about the gpfsug-discuss mailing list