<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Exporting the filesystem to the remove cluster as RO is an
excellent idea and works if all remote clients only need RO.<br>
</p>
<p>Alternatively (and I believe this is still the case) you can set
the "ro" filesystem mount option in the file
"/var/mmfs/etc/localMountOptions" or
"/var/mmfs/etc/localMountOptions.<YOURFSNAME>" on all nodes.</p>
<p>The issue with changing /etc/fstab is that in my experience GPFS
has been known to override it.<br>
</p>
<p>-- Lauz<br>
</p>
<div class="moz-cite-prefix">On 04/03/2020 11:24, Jan-Frode
Myklebust wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHwPathVrLAmoHfh5C2Hi4Xv8CCU0XP4ziWCKAXgrZyZ40hNqA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>
<div><br>
</div>
<div dir="auto">I don’t know the answer — but as an alternative
solution, have you considered splitting the read only clients
out into a separate cluster. Then you could enforce the
read-only setting using «mmauth grant ... -a ro».</div>
</div>
<div>
<div dir="auto"><br>
</div>
<div dir="auto">That should be supported.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"> -jf</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">ons. 4. mar. 2020 kl.
12:05 skrev Agostino Funel <<a
href="mailto:agostino.funel@enea.it" target="_blank"
moz-do-not-send="true">agostino.funel@enea.it</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
we have a GPFS cluster version 4.2.3.19. We have seen in
the official <br>
"Administration and Programming Reference" (version 4
Release 2.0, pag. <br>
28) that the read-only mount option (-o ro) is not
explicitly cited. <br>
This option is supported in version 5.*.<br>
<br>
However we tried, as a test, the -o ro mount option on two
clients with <br>
the following SO and kernels<br>
<br>
client 1<br>
<br>
CentOS Linux release 7.3.1611 (Core)<br>
uname -r<br>
3.10.0-514.26.2.el7.x86_64<br>
<br>
<br>
client 2<br>
<br>
CentOS release 6.4 (Final)<br>
uname -r<br>
2.6.32-358.23.2.el6.x86_64<br>
<br>
and it worked fine.<br>
<br>
The -o ro option is non permanent in the sense that
unmounting and <br>
remounting the file system on these clients it turned in
r/w original state.<br>
<br>
Now, we have the necessity of setting read-only the file
system on all <br>
clients of our cluster.<br>
<br>
The question is: could we safely use the -o ro option for
all clients <br>
even if this option is not cited in the official (v. 4
release 2.0) <br>
documentation?<br>
<br>
Thank you very much.<br>
<br>
Best regards,<br>
<br>
Agostino Funel<br>
<br>
<br>
<br>
<br>
-- <br>
Agostino Funel<br>
DTE-ICT-HPC<br>
ENEA<br>
P.le E. Fermi 1<br>
80055 Portici (Napoli) Italy<br>
Phone: (+39) 081-7723575<br>
Fax: (+39) 081-7723344<br>
E-mail: <a href="mailto:agostino.funel@enea.it"
target="_blank" moz-do-not-send="true">agostino.funel@enea.it</a><br>
WWW: <a href="http://www.afs.enea.it/funel"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.afs.enea.it/funel</a><br>
<br>
<br>
<br>
==================================================<br>
<br>
Questo messaggio e i suoi allegati sono indirizzati
esclusivamente alle persone indicate e la casella di posta
elettronica da cui e' stata inviata e' da qualificarsi
quale strumento aziendale.<br>
La diffusione, copia o qualsiasi altra azione derivante
dalla conoscenza di queste informazioni sono rigorosamente
vietate (art. 616 c.p, D.Lgs. n. 196/2003 s.m.i. e GDPR
Regolamento - UE 2016/679).<br>
Qualora abbiate ricevuto questo documento per errore siete
cortesemente pregati di darne immediata comunicazione al
mittente e di provvedere alla sua distruzione. Grazie.<br>
<br>
This e-mail and any attachments is confidential and may
contain privileged information intended for the
addressee(s) only.<br>
Dissemination, copying, printing or use by anybody else is
unauthorised (art. 616 c.p, D.Lgs. n. 196/2003 and
subsequent amendments and GDPR UE 2016/679).<br>
If you are not the intended recipient, please delete this
message and any attachments and advise the sender by
return e-mail. Thanks.<br>
<br>
==================================================<br>
<br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://spectrumscale.org"
rel="noreferrer" target="_blank" moz-do-not-send="true">spectrumscale.org</a><br>
<a
href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a><br>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a>
</pre>
</blockquote>
</body>
</html>