guys, actually, the original cmds i ran did have the = signs for the --failnode=<nodename> arguments; i gave the wrong bash history info to kevin to analyse when he asked for them from the host :)
however, having said that, it's the NIDs that were missing from the hosts that fixed the issues i was having. cheers Kevin Van Maren wrote: > Kevin Van Maren wrote: >> Brian J. Murrell wrote: >>> On Tue, 2008-11-25 at 23:34 +0000, neil rutter wrote: >>> >>>> kevin, brian, >>>> >>>> thanks to you both. i had a mkfs.lustre error, which after had been >>>> pointed out fixed the issue. >>>> >>> Can you share the error here so that future searches of this problem are >>> complete with a solution? >>> >>> There's nothing more frustrating than finding the same problem you are >>> having in a mailing list archive and with no solution. Actually there >>> is something more frustrating and that's that the problem was solved but >>> no details on how. >>> >>> Thanx, >>> b. >>> >> Come on, if we wanted to make it that easy, it would be in the manual ;-) >> >> I gave Neil the correct mkfs commands: >> >> mkfs.lustre --reformat [EMAIL PROTECTED] --mgs /dev/sdb >> mkfs.lustre --reformat --fsname bananafs >> [EMAIL PROTECTED] [EMAIL PROTECTED] >> [EMAIL PROTECTED] --mdt /dev/sdc >> >> Kevin > > Brian, > > Here are the original, incorrect, mkfs commands: > > mkfs.lustre --reformat --fsname bananafs --failnode lustremds2 --mgs > /dev/sdb > mkfs.lustre --reformat --fsname bananafs --failnode lustremds2 > --mgsnode=lustremds1 --mdt /dev/sdc > > Kevin > > _______________________________________________ > Lustre-discuss mailing list > [email protected] > http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
