Re: failover questions after upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2006-11-21 at 09:14 -0500, jason@xxxxxxxxxxxxxx wrote:
> while it was in the failed state, I did 
>  service rgmanager stop ; service rgmanager start
> 
> and got the following.
> 
> Nov 17 18:52:06 tf1 clurgmgrd: [17992]: <warning> Device /dev/mapper/diskarray-lv1 is mounted 
> on /mnt/gfs instead of /mnt/gfs/htdocs 
> Nov 17 18:52:06 tf1 clurgmgrd: [17992]: <info> unmounting /mnt/gfs/htdocs 
> Nov 17 18:52:06 tf1 clurgmgrd: [17992]: <err> 'umount /mnt/gfs/htdocs' failed, error=0 
> Nov 17 18:52:06 tf1 clurgmgrd[17992]: <notice> stop on fs "apache_content" returned 2 (invalid 
> argument(s)) 
> Nov 17 18:52:06 tf1 clurgmgrd[17992]: <info> Services Initialized 
> Nov 17 18:52:06 tf1 clurgmgrd[17992]: <info> Logged in SG "usrm::manager" 
> Nov 17 18:52:06 tf1 clurgmgrd[17992]: <info> Magma Event: Membership Change 
> Nov 17 18:52:06 tf1 clurgmgrd[17992]: <info> State change: Local UP 
> Nov 17 18:52:06 tf1 clurgmgrd[17992]: <info> State change: tf2 UP 
> 
> but I never see anything about the ip address..

Your mount point in /etc/fstab and cluster.conf should match
(/mnt/gfs/htdocs should match /mnt/gfs).

You can also disable 'force unmount' for GFS if you want.

-- Lon

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux