The manual does not make much sense when it comes to MGS failover. Manual: Note ? The MGS does not use the --failnode option. You need to set the command on all other nodes of the filesystem (servers and clients), about the failover options for the MGS. Use the --mgsnode parameter on servers and mount address for clients. The servers need to contact the MGS for configuration information; they cannot query the MGS about the failover partner. This does not make any sense at all, other than you can''t use -- failnode and that clients can''t check with two different hosts for MGS data. Our MGS will be on its own LUN setup with heartbeat between two nodes that are also working as an MDS pair. While Heartbeat takes care of mounting the MGS file system, how can we tell clients "if mds1 is down use mds2 for MGS data" Thanks. I hope that makes sense. Brock Palen www.umich.edu/~brockp Center for Advanced Computing brockp at umich.edu (734)936-1985
On Wed, 2008-07-30 at 09:48 -0400, Brock Palen wrote:> The manual does not make much sense when it comes to MGS failover. > > Manual: > > Note ? The MGS does not use the --failnode option.This is true.> You need to set the > command on all other nodes of the filesystem (servers and clients), > about the > failover options for the MGS.This is true also.> Use the --mgsnode parameter on servers > and mount > address for clients.Also true.> The servers need to contact the MGS for > configuration > information;Also true.> they cannot query the MGS about the failover partner.This part is either unclear or wrong. I guess the question is what the writer was referring to as "they". You could file a bug about that.> This does not make any sense at all, other than you can''t use -- > failnodeOn the MGS, yes. On servers, yes you can use that option.> and that clients can''t check with two different hosts for > MGS data.They sure can! That''s what the "<mgsspec>:=<mgsnode>[:<mgsnode>]" syntax in the mount.lustre manpage is all about.> Our MGS will be on its own LUN setup with heartbeat > between two nodes that are also working as an MDS pair.Good.> While > Heartbeat takes care of mounting the MGS file system, how can we tell > clients "if mds1 is down use mds2 for MGS data"$ man mount.lustre Check out mgsspec in the OPTIONS section. b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080730/e0c91e31/attachment.bin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thank you, I was only looking at the mkfs.lustre didn''t think the hosts are the ones that need to look there, not mgs filesystem its self. does the mgsspec also work for --mgsnode= when creating a file system? mkfs.lustre .... --mgsnodes=mds1 at tcp0:mds2 at tcp0 Would that be valid? Brock Palen www.umich.edu/~brockp Center for Advanced Computing brockp at umich.edu (734)936-1985 On Jul 30, 2008, at 10:29 AM, Brian J. Murrell wrote:> On Wed, 2008-07-30 at 09:48 -0400, Brock Palen wrote: >> The manual does not make much sense when it comes to MGS failover. >> >> Manual: >> >> Note ? The MGS does not use the --failnode option. > > This is true. > >> You need to set the >> command on all other nodes of the filesystem (servers and clients), >> about the >> failover options for the MGS. > > This is true also. > >> Use the --mgsnode parameter on servers >> and mount >> address for clients. > > Also true. > >> The servers need to contact the MGS for >> configuration >> information; > > Also true. > >> they cannot query the MGS about the failover partner. > > This part is either unclear or wrong. I guess the question is what > the > writer was referring to as "they". You could file a bug about that. > >> This does not make any sense at all, other than you can''t use -- >> failnode > > On the MGS, yes. On servers, yes you can use that option. > >> and that clients can''t check with two different hosts for >> MGS data. > > They sure can! That''s what the "<mgsspec>:=<mgsnode>[:<mgsnode>]" > syntax in the mount.lustre manpage is all about. > >> Our MGS will be on its own LUN setup with heartbeat >> between two nodes that are also working as an MDS pair. > > Good. > >> While >> Heartbeat takes care of mounting the MGS file system, how can we tell >> clients "if mds1 is down use mds2 for MGS data" > > $ man mount.lustre > > Check out mgsspec in the OPTIONS section. > > b. > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) iD8DBQFIkH5JMFCQB4Bvz5QRArwBAJ0TBBFVIBWiLQIt1e6kbG/n6Ufn5wCcCx1L /KJFr81OkKkuTTW0N4LtcUk=hfmn -----END PGP SIGNATURE-----
On Wed, 2008-07-30 at 10:44 -0400, Brock Palen wrote:> > does the mgsspec also work for --mgsnode= when creating a file system?It''s supposed to. Beware of bug 15912 however. b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20080730/33bc5392/attachment.bin
Hi, take a look at section 32.4.3: # mount -t lustre 10.10.0.5 at tcp0:10.10.0.6 at tcp0:/mds-p/client /mnt/lustre means if 10.10.0.5 at tcp0 is down use 10.10.0.6 at tcp0 for MGS. Regards, Stephane Thiell CEA Brock Palen a ?crit :> The manual does not make much sense when it comes to MGS failover. > > Manual: > > Note ? The MGS does not use the --failnode option. You need to set the > command on all other nodes of the filesystem (servers and clients), > about the > failover options for the MGS. Use the --mgsnode parameter on servers > and mount > address for clients. The servers need to contact the MGS for > configuration > information; they cannot query the MGS about the failover partner. > > This does not make any sense at all, other than you can''t use -- > failnode and that clients can''t check with two different hosts for > MGS data. Our MGS will be on its own LUN setup with heartbeat > between two nodes that are also working as an MDS pair. While > Heartbeat takes care of mounting the MGS file system, how can we tell > clients "if mds1 is down use mds2 for MGS data" > > Thanks. I hope that makes sense. > > > Brock Palen > www.umich.edu/~brockp > Center for Advanced Computing > brockp at umich.edu > (734)936-1985 > > > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss