On 2011-01-27, at 08:26, Jason Rappleye wrote: > On Jan 27, 2011, at 3:15 AM, Andreas Dilger wrote: >> >> The problem is that the client will only connect to a single MGS for >> configuration updates (in particular, the MGS for the last filesystem that >> was mounted). If there is a configuration change (e.g. lctl conf_param, or >> adding a new OST) on one of the other filesystems, then the client will not >> be notified of this change because it is no longer connected to the MGS for >> that filesystem. >> >> Granted, it is possible that someone fixed this when I wasn't paying >> attention. > > I thought this sounded familiar - have a look at bz 20299. Multiple MGCs on a > client are ok; multiple MGSes on a single server are not.
Sigh, it was even me who filed the bug... Seems that bit of information was evicted from my memory. Thanks for setting me straight. Cheers, Andreas -- Andreas Dilger Principal Engineer Whamcloud, Inc. _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
