Kevin you are correct, it is one "system" storage pool per file system not cluster.

Fred
__________________________________________________
Fred Stock | IBM Pittsburgh Lab | 720-430-8821
[email protected]
 
 
----- Original message -----
From: "Buterbaugh, Kevin L" <[email protected]>
Sent by: [email protected]
To: gpfsug main discussion list <[email protected]>
Cc:
Subject: Re: [gpfsug-discuss] GPFS v5: Blocksizes and subblocks
Date: Wed, Mar 27, 2019 10:33 AM
 
Hi All,
 
So I was looking at the presentation referenced below and it states - on multiple slides - that there is one system storage pool per cluster.  Really?  Shouldn’t that be one system storage pool per filesystem?!?  If not, please explain how in my GPFS cluster with two (local) filesystems I see two different system pools with two different sets of NSDs, two different capacities, and two different percentages full???
 
Thanks…
 
Kevin
 
Kevin Buterbaugh - Senior System Administrator
Vanderbilt University - Advanced Computing Center for Research and Education
[email protected] - (615)875-9633
 
On Mar 26, 2019, at 11:27 AM, Dorigo Alvise (PSI) <[email protected]> wrote:
 
Hi Marc,
"Indirect block size" is well explained in this presentation: 
 
 
pages 37-41
 
Cheers,
 
   Alvise
 

From: [email protected] [[email protected]] on behalf of Caubet Serrabou Marc (PSI) [[email protected]]
Sent: Tuesday, March 26, 2019 4:39 PM
To: gpfsug main discussion list
Subject: [gpfsug-discuss] GPFS v5: Blocksizes and subblocks

 
 
Hi all,
 
according to several GPFS presentations as well as according to the man pages:
 
         Table 1. Block sizes and subblock sizes

+-------------------------------+-------------------------------+
| Block size                    | Subblock size                 |
+-------------------------------+-------------------------------+
| 64 KiB                        | 2 KiB                         |
+-------------------------------+-------------------------------+
| 128 KiB                       | 4 KiB                         |
+-------------------------------+-------------------------------+
| 256 KiB, 512 KiB, 1 MiB, 2    | 8 KiB                         |
| MiB, 4 MiB                    |                               |
+-------------------------------+-------------------------------+
| 8 MiB, 16 MiB                 | 16 KiB                        |
+-------------------------------+-------------------------------+

 
A block size of 8MiB or 16MiB should contain subblocks of 16KiB.
 
However, when creating a new filesystem with 16MiB blocksize, looks like is using 128KiB subblocks:
 
[root@merlindssio01 ~]# mmlsfs merlin
flag                value                    description
------------------- ------------------------ -----------------------------------
 -f                 8192                     Minimum fragment (subblock) size in bytes (system pool)
                    131072                   Minimum fragment (subblock) size in bytes (other pools)
 -i                 4096                     Inode size in bytes
 -I                 32768                    Indirect block size in bytes
.
.
.
 -n                 128                      Estimated number of nodes that will mount file system
 -B                 1048576                  Block size (system pool)
                    16777216                 Block size (other pools)
.
.
.
 
What am I missing? According to documentation, I expect this to be a fixed value, or it isn't at all?
 
On the other hand, I don't really understand the concept 'Indirect block size in bytes', can somebody clarify or provide some details about this setting?
 
Thanks a lot and best regards,
Marc               
_________________________________________
Paul Scherrer Institut 
High Performance Computing
Marc Caubet Serrabou
Building/Room: WHGA/019A
Forschungsstrasse, 111
5232 Villigen PSI
Switzerland

Telephone: +41 56 310 46 67
E-Mail: [email protected]
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
https://nam04.safelinks.protection.outlook.com/?url="">
 

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Reply via email to