Re: problems with iscsi storage and boot order

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

 



Thanks, I'll try upping the retries. I am assuming this is the same thing as increasing the time value here:

# To specify the time to wait for login to complete, edit the line.
# The value is in seconds and the default is 15 seconds.
node.conn[0].timeo.login_timeout = 25

I have put the priorities back too.   That was just for testing purposes.

Randy

gordan@xxxxxxxxxx wrote:
On Mon, 22 Oct 2007, Randy Brown wrote:

If I boot both nodes with none of the clustering components (cman, clvmd, gfs, or rgmanager) starting at boot, I can restart the iscsi service then start cman, clvmd, gfs, and rgmanger and everything works. The problem stems from the iscsi not making a successful connection to the storage when the iscsi service starts so clvmd doesn't see the volume group so gfs can't mount the filesystem.

Up the number of connection retries in iscsi.conf.

I have tried moving things around in the boot order using chkconfig, i.e., moved iscsi to S68, cman to S70, clvmd to S72, and gfs to S74 at runlevels 2, 3, 4, and 5, but that didn't make any difference.

Bad idea. I _strongly_ suggest you put the priorities back as whey were.

Gordan

--
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

[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