Ahh, forgot about the gfs2 service. Been a long time since I've set GFS1/2 up. I'll go crawl back into my cave now... -C On Thu, Jun 9, 2011 at 4:20 PM, Digimer <linux@xxxxxxxxxxx> wrote: > On 06/09/2011 10:46 AM, Budai Laszlo wrote: >> >> Hi, >> >> What should be done in order to mount a gfs file system at boot? >> I've created the following line in /etc/fstab: >> >> /dev/clvg/gfsvol /mnt/testgfs gfs defaults 0 >> 0 >> >> but it is not mounting the fs at boot. If I run "mount -a" then the fs >> will get mounted. >> Is there any option for fstab to specify that this mount should be >> delayed until the cluster is up and running? >> >> Thank you, >> Laszlo > > The trick is that you need to setup the GFS2 partition with > "rw,suid,dev,exec,nouser,async" instead of "defaults". This is because > "defaults" implies "auto", and the cluster is not online that early in the > boot process. > > To have it mount on boot, start the cluster (chkconfig cman on). If you > defined GFS2 as a managed resource, then also enable rgmanager at boot. If > not, then instead, enable "gfs2" at boot. > > If you're not using RHCS, then the same should still work. You just need to > ensure that the service that provides quorum (corosync in pacemaker) starts > so that the cluster can form and provide DLM, which is needed by GFS2. With > DLM, then it's a matter of starting the resource manager > (pacemaker/rgmanager) if the partitions are managed, or starting GFS2 which > will consult /etc/fstab and mount any found GFS2 partitions. > > -- > Digimer > E-Mail: digimer@xxxxxxxxxxx > Freenode handle: digimer > Papers and Projects: http://alteeve.com > Node Assassin: http://nodeassassin.org > "I feel confined, only free to expand myself within boundaries." > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster > -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
