[gpfsug-discuss] Restriping GPFS Metadata

[Buterbaugh, Kevin L]

Hi Marc,

Unfortunately, I find the first paragraph of your response … confusing.  :-O

I understand your 1st sentence … but isn’t one of the benefits of having only metadata disks in the system pool the ability to then have separate block sizes for your metadata and your data?  If so, isn’t the simplest way to do that to have metadataOnly and dataOnly disks?  I recognize that they may not be the *only* way to accomplish that…

Kevin

On Dec 10, 2015, at 11:26 AM, Marc A Kaplan <makaplan at us.ibm.com<mailto:makaplan at us.ibm.com>> wrote:

The concept of "metadata" disks pre-dates the addition of POOLs.  Correct use of policy SET POOL rules and assignment of disks or SSDs to pools makes
metadata only disks a redundant, potentially confusing concept that the new comer to GPFS (ahem... Spectrum Scale FS) can ignore.

Metadata always goes to system pool.  Other file data can be directed or MIGRATed to any pool you like, using SET POOL or MIGRATE rules.


<ATT00001.gif>
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org<http://spectrumscale.org>
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

—
Kevin Buterbaugh - Senior System Administrator
Vanderbilt University - Advanced Computing Center for Research and Education
Kevin.Buterbaugh at vanderbilt.edu<mailto:Kevin.Buterbaugh at vanderbilt.edu> - (615)875-9633



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20151210/5014ef25/attachment-0002.htm>