[gpfsug-discuss] cross-cluster mounting different versions of gpfs

[Sven Oehme]

while this is all correct people should think twice about doing this.
if you create a filesystem with older versions, it might prevent you from
using some features like data-in-inode, encryption, adding 4k disks to
existing filesystem, etc even if you will eventually upgrade to the latest
code.

for some customers its a good point in time to also migrate to larger
blocksizes compared to what they run right now and migrate the data. i have
seen customer systems gaining factors of performance improvements even on
existing HW by creating new filesystems with larger blocksize and latest
filesystem layout (that they couldn't before due to small file waste which
is now partly solved by data-in-inode). while this is heavily dependent on
workload and environment its at least worth thinking about.

sven



On Wed, Mar 16, 2016 at 4:20 PM, Marc A Kaplan <makaplan at us.ibm.com> wrote:

> The key point is that you must create the file system so that is "looks"
> like a 3.5 file system.  See mmcrfs ... --version.  Tip: create or find a
> test filesystem back on the 3.5 cluster and look at the version string.
>  mmslfs xxx -V.  Then go to the 4.x system and try to create a file system
> with the same version string....
>
>
> [image: Marc A Kaplan]
>
> _______________________________________________
> 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/20160316/49c8c5af/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 21994 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160316/49c8c5af/attachment-0002.gif>