<div dir="ltr">That's the winner.<div><br></div><div>ps aux |grep glusterfs shows the options being used. </div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jan 12, 2014 at 7:45 PM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 01/11/2014 02:43 AM, Justin Dossey wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm in the process of configuring all my 32-bit FUSE clients to use<br>
enable-ino32 on mount and noticed that the mount command (with no<br>
options) does not report whether that flag is being used.<br>
<br>
I want to test programatically whether the enable-ino32 flag is being<br>
used on the current mount so I can automate the remount. Ideally I<br>
would be able to have puppet unmount and remount the filesystem if the<br>
options in fstab don't match the options on the mounted filesystem.<br>
<br>
Any ideas?<br>
<br>
</blockquote>
<br></div></div>
Most mount options do get passed on as arguments to the corresponding glusterfs client process which is responsible for the mount. You can possibly check the command line of the client process to determine if mount options of interest are being used.<span class="HOEnZb"><font color="#888888"><br>
<br>
-Vijay<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Justin Dossey<br>CTO, PodOmatic<div><br></div>
</div>