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

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

?Hi,


Earlier today I made a change to mfsexports.cfg and then forced mfsmaster to perform a configuration reload by sending a HUP signal to the mfsmaster process.  At that point, all my client MooseFS mounts became empty.  The mount points were still in /proc/self/mountinfo and it looks like any open files were still accessible.  But to make the MooseFS filesystem visible and accessible again, I had to unmount it and then mount it again on each of my clients.  I've made changes to mfsexports.cfg and forced mfsmaster to reload in the past  (probably when I was still using MooseFS 2.x) but I never had a problem like this.  I'm using version 3.0.81.  Has anyone else seen this?  I don't have a test environment to try this again otherwise I would do it again and make sure that it's repeatable and not just some strange but rare fluke.


Thanks!


Steve