Just for clarification, this RFE is for changing the name of the Network Shared
Disk device used to store data for file systems, not a NSD I/O server node name,
-Bryan
From: gpfsug-discuss-boun...@spectrumscale.org
On Behalf Of Christopher Black
Sent: Tuesday, December 1, 2020 1:26 PM
To:
Thanks very much for your feedback Chris.
Renata
On Tue, 1 Dec 2020, Christopher Black wrote:
>We tune vm-related sysctl values on our gpfs clients.
>These are values we use for 256GB+ mem hpc nodes:
>vm.min_free_kbytes=2097152
>vm.dirty_bytes = 3435973836
>vm.dirty_background_bytes =
Hey all...
Hope all your clusters are up and performing well...
Got a new RFE (I searched and didn't find anything like it) for your
consideration. The ability to change the name of an existing NSD:
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=147125
We embed information
+1 from me.
Someone did a building block install for us and named a couple io nodes with
initial upper case (unlike all other unix hostnames in our env which are all
lowercase). For a while it just bothered us, and we complained occasionally to
hear that it was not easy to change. Over two
We tune vm-related sysctl values on our gpfs clients.
These are values we use for 256GB+ mem hpc nodes:
vm.min_free_kbytes=2097152
vm.dirty_bytes = 3435973836
vm.dirty_background_bytes = 1717986918
The vm.dirty parameters are to prevent NFS from buffering huge amounts of
writes and then pushing
On 01/12/2020 19:07, Christopher Black wrote:
CAUTION: This email originated outside the University. Check before clicking
links or attachments.
We tune vm-related sysctl values on our gpfs clients.
These are values we use for 256GB+ mem hpc nodes:
vm.min_free_kbytes=2097152
vm.dirty_bytes =
Hi, some of our gpfs clients will get stale file handles for gpfs
mounts and it seems to be related to memory depletion. Even after the
memory is freed though gpfs will continue be unavailable and df will
hang. I have read about setting vm.min_free_kbytes as a possible fix
for this, but wasn't
Dave Johnson at d...@brown.edu asks:
When GPFS needs to add inodes to the filesystem, it seems to pre-create
about 4 million of them.
Judging by the logs, it seems it only takes a few (13 maybe) seconds to
do this.
However we are suspecting that this might only be to request the
