<div dir="ltr">Hi Gareth:<div><br></div><div>We have the spectrum archive product with encryption. It encrypts data on disk and tape...but not metadata. We originally had hoped to write small files with metadata...that does not happen with encryption.</div><div><br></div><div>My guess is that the system pool(where metadata lives) cannot be encrypted.</div><div><br></div><div>So you may pay a performance penalty for small files using encryption depending on what backends your data write policy.</div><div><br></div><div><br></div><div>Eric</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 26, 2018 at 7:25 AM, Gareth Horton <span dir="ltr"><<a href="mailto:G.Horton@bham.ac.uk" target="_blank">G.Horton@bham.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi. All,<br>
<br>
I would be interested to hear if any members have experience implementing Encryption?, any gotchas, tips or any other information which may help with the preparation and implementation stages would be appreciated.<br>
<br>
I am currently reading through the documentation and reviewing the preparation steps, and with a scheduled maintenance window on the horizon it would be a good opportunity to carry out any preparatory steps requiring an outage.<br>
<br>
If there are any aspects of the configuration which in hindsight could have been done at the preparation stage this would be especially useful.<br>
<br>
Many Thanks<br>
<br>
Gareth<br>
<br>
----------------------<br>
<br>
On 24/03/2018, 12:00, "<a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">gpfsug-discuss-bounces@<wbr>spectrumscale.org</a> on behalf of <a href="mailto:gpfsug-discuss-request@spectrumscale.org">gpfsug-discuss-request@<wbr>spectrumscale.org</a>" <<a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">gpfsug-discuss-bounces@<wbr>spectrumscale.org</a> on behalf of <a href="mailto:gpfsug-discuss-request@spectrumscale.org">gpfsug-discuss-request@<wbr>spectrumscale.org</a>> wrote:<br>
<br>
Send gpfsug-discuss mailing list submissions to<br>
<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.<wbr>org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" rel="noreferrer" target="_blank">http://gpfsug.org/mailman/<wbr>listinfo/gpfsug-discuss</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:gpfsug-discuss-request@spectrumscale.org">gpfsug-discuss-request@<wbr>spectrumscale.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:gpfsug-discuss-owner@spectrumscale.org">gpfsug-discuss-owner@<wbr>spectrumscale.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of gpfsug-discuss digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Reminder - SSUG-US Spring meeting - Call for Speakers and<br>
Registration (Oesterlin, Robert)<br>
2. Pool layoutMap option changes following GPFS upgrades<br>
(Caron, Paul)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Fri, 23 Mar 2018 12:59:51 +0000<br>
From: "Oesterlin, Robert" <<a href="mailto:Robert.Oesterlin@nuance.com">Robert.Oesterlin@nuance.com</a>><br>
To: gpfsug main discussion list <<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.<wbr>org</a>><br>
Subject: [gpfsug-discuss] Reminder - SSUG-US Spring meeting - Call for<br>
Speakers and Registration<br>
Message-ID: <<a href="mailto:28FF6725-9698-4F68-BC4E-BBCD6164BB3D@nuance.com">28FF6725-9698-4F68-BC4E-<wbr>BBCD6164BB3D@nuance.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Reminder: The registration for the Spring meeting of the SSUG-USA is now open. This is a Free two-day and will include a large number of Spectrum Scale updates and breakout tracks.<br>
<br>
Please note that we have limited meeting space so please register early if you plan on attending. If you are interested in presenting, please contact me. We do have a few more slots for user presentations ? these do not need to be long.<br>
<br>
You can register here:<br>
<br>
<a href="https://www.eventbrite.com/e/spectrum-scale-gpfs-user-group-us-spring-2018-meeting-tickets-43662759489" rel="noreferrer" target="_blank">https://www.eventbrite.com/e/<wbr>spectrum-scale-gpfs-user-<wbr>group-us-spring-2018-meeting-<wbr>tickets-43662759489</a><br>
<br>
DATE AND TIME<br>
Wed, May 16, 2018, 9:00 AM ?<br>
Thu, May 17, 2018, 5:00 PM EDT<br>
<br>
LOCATION<br>
IBM Cambridge Innovation Center<br>
One Rogers Street<br>
Cambridge, MA 02142-1203<br>
<br>
<br>
Bob Oesterlin<br>
Sr Principal Storage Engineer, Nuance<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180323/824dbcdc/attachment-0001.html" rel="noreferrer" target="_blank">http://gpfsug.org/pipermail/<wbr>gpfsug-discuss/attachments/<wbr>20180323/824dbcdc/attachment-<wbr>0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 23 Mar 2018 20:10:05 +0000<br>
From: "Caron, Paul" <<a href="mailto:Paul.Caron@sig.com">Paul.Caron@sig.com</a>><br>
To: "<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.<wbr>org</a>"<br>
<<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.<wbr>org</a>><br>
Subject: [gpfsug-discuss] Pool layoutMap option changes following GPFS<br>
upgrades<br>
Message-ID: <<a href="mailto:980f9a27290342e28197154b924d0abf@msx.bala.susq.com">980f9a27290342e28197154b924d0<wbr>abf@msx.bala.susq.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi,<br>
<br>
Has anyone run into a situation where the layoutMap option for a pool changes from "scatter" to "cluster" following a GPFS software upgrade? We recently upgraded a file system from 3.5.0.21, to 4.1.1.17, and finally to 4.2.3.6. We noticed that the layoutMap option for two of our pools changed following the upgrades. We didn't recreate the file system or any of the pools. Further lab testing has revealed that the layoutMap option change actually occurred during the first upgrade to 4.1.1.17, and it was simply carried forward to 4.2.3.6. We have a PMR open with IBM on this problem, but they have told us that layoutMap option changes are impossible for existing pools, and that a software upgrade couldn't do this. I sent the results of my lab testing today, so I'm hoping to get a better response.<br>
<br>
We would rather not have to recreate all the pools, but it is starting to look like that may be the only option to fix this. Also, it's unclear if this could happen again during future upgrades.<br>
<br>
Here's some additional background.<br>
<br>
* The "-j" option for the file system is "cluster"<br>
<br>
* We have a pretty small cluster; just 13 nodes<br>
<br>
* When reproducing the problem, we noted that the layoutMap option didn't change until the final node was upgraded<br>
<br>
* The layoutMap option changed before running the "mmchconfig release=LATEST" and "mmchfs <fs> -V full" commands, so those don't seem to be related to the problem<br>
<br>
Thanks,<br>
<br>
Paul C.<br>
SIG<br>
<br>
<br>
______________________________<wbr>__<br>
<br>
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20180323/181b0ac7/attachment-0001.html" rel="noreferrer" target="_blank">http://gpfsug.org/pipermail/<wbr>gpfsug-discuss/attachments/<wbr>20180323/181b0ac7/attachment-<wbr>0001.html</a>><br>
<br>
------------------------------<br>
<br>
______________________________<wbr>_________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://spectrumscale.org" rel="noreferrer" target="_blank">spectrumscale.org</a><br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" rel="noreferrer" target="_blank">http://gpfsug.org/mailman/<wbr>listinfo/gpfsug-discuss</a><br>
<br>
<br>
End of gpfsug-discuss Digest, Vol 74, Issue 45<br>
******************************<wbr>****************<br>
<br>
<br>
______________________________<wbr>_________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://spectrumscale.org" rel="noreferrer" target="_blank">spectrumscale.org</a><br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" rel="noreferrer" target="_blank">http://gpfsug.org/mailman/<wbr>listinfo/gpfsug-discuss</a><br>
</blockquote></div><br></div>