Hide Forgot
Description of problem: Should /etc/init.d/netfs mount GFS2 filesystems when there is a /etc/init.d/gfs2 separate init script? netfs has a line: action $"Mounting other filesystems: " mount -a -t nonfs,nfs4,cifs,ncpfs,gfs If so, what is GFS2's init script really for?
gfs != gfs2 and since this is rhel6, gfs doesn't even exist. The gfs2 init script does mount the gfs2 filesystems, however this is not really correct. We have a bug open which is bug #435906 which is requesting a change to allow these mounts to work correctly. This is currently blocked on upstream work. I've not heard anything recently about progress.
That line means it should *not* mount gfs filesystems... probably needs expanded to GFS2. Just FYI.
gfs may not equal gfs2 but the /etc/init.d/netfs tried to mount GFS2 filesystems even though it says "gfs" in the mount line! Until upstream work is complete and given plain gfs is gone, should it not just have this removed from netfs?
As I said, that line is telling it to *not* mount gfs (or nfs, or ncpfs) filesystems. So it's expected that that line might mount gfs2.
Ahh, sorry all is clear.
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
So do we still need this bug now? or is there nothing to fix.
It's still trying to mount gfs2 filesystems in /etc/init.d/netfs as far as I can see (not sure if fixed in 6.1). I thought we'd decided it shouldn't be and this needs to be fixed (the gfs2 startup script does this).
Created attachment 516109 [details] Patch to fix the netfs script for gfs2 I think this is all that needs doing... this will ensure that gfs2 is not mounted as part of "all the other filesystems" from netfs and thus will be left for the gfs2 script to mount/umount.
Looks reasonable.
That is commit 2d3dfa0 on master, FWIW.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1528.html