Re: [MooseFS-Users] mfsmaster config reload breaks client mounts?

[Wilson, S. M <st...@pu...>]

Hi Aleksander,


I needed to add another line to mfsexports.cfg today.  I didn't change any existing lines; I just added the following line:

    10.163.216.88   /       rw,alldirs,maproot=0


After adding this line, I took a deep breath and then sent a HUP signal to the mfsmaster process.  ?Rats...  all the clients for that MooseFS server immediately had empty mount points.


This occurred on a different MooseFS master server than the one mentioned in my original email.  The version of this mfsmaster is 3.0.78.  This time I did not use Ansible but instead manually edited the mfsexports.cfg file and manually sent a HUP signal to mfsmaster process.


Unfortunately, this looks like a reproducible problem in my environment and not just a one-time fluke.


Is there any additional information that I can send to be of help to you?  The clients and server are running on Ubuntu 16.04.


Best regards,

Steve


________________________________
From: Wilson, Steven M <st...@pu...>
Sent: Monday, September 12, 2016 9:28 AM
To: Aleksander Wieliczko; Krzysztof Kielak
Cc: MooseFS-Users
Subject: Re: [MooseFS-Users] mfsmaster config reload breaks client mounts?


?Hi Aleksander,


Thanks for attempting to reproduce the problem in your environment.  I'll send the mfsexports.cfg files to you (prior to the change and after the change).  I use Ansible for configuration management and I normally make all changes on my Ansible server in a file of my own format that is then used to build mfsexports.cfg files on each MooseFS master server.  So I'll also send the script that Ansible calls to build the mfsexports.cfg file and issue a HUP signal to mfsmaster.


Thanks,

Steve


________________________________
From: Aleksander Wieliczko <ale...@mo...>
Sent: Monday, September 12, 2016 6:25 AM
To: Wilson, Steven M; Krzysztof Kielak
Cc: MooseFS-Users
Subject: Re: [MooseFS-Users] mfsmaster config reload breaks client mounts?

Hi,

I would like to inform you that we are not able to reproduce this problem in our development environment.
Also I would like to add that in MooseFS is scenario which can cause mfsmount session drop.
When you change permissions in mfsexports.cfg file for connected mounts and you send HUP signal, MooseFS master will check permissions again, and if permissions have been changed access to cluster will be denied.

We have another question for you.
Can you send us old and new "mfsexports.cfg" files, so we will be able to understand what had happened?

You can send it to dwt[at]moosefs.com

Best regards
Aleksander Wieliczko
Technical Support Engineer
MooseFS.com<moosefs.com>