On the weekend I moved our lustre filesystem configuration from a single MGS to a failover MGS / MDS with heartbeat and got it going. I had to run tunefs.lustre on all OSS / MGS / MDS servers. I had some issues with mounting the OSTs on the new failover mgs and could only mount them with the following command: tunefs.lustre --writeconf --erase-params --mgsnode=172.16.16.5 --param="mdt.group_upcall=NONE" /dev/mapper/mpath8p1 Rather than the command I ran on all other servers: tunefs.lustre --dryrun --fsname=AC3 --mdt --mgsnode=172.16.16.5 --failnode=172.16.16.6 /dev/mapper/mpath7p1 I have no idea. Anyway, whatever. So I am adding a new OST to the failover MGS and ran this command: mkfs.lustre --ost —mgsnode=172.16.16.5 --failnode=172.16.16.6 --param="mdt.group_upcall=NONE" /dev/mapper/mpath7p2 but it doesn’t mount - I guess I should have known. I then ran the: tunefs.lustre --writeconf --erase-params --mgsnode=172.16.16.5 --param="mdt.group_upcall=NONE" /dev/mapper/mpath7p2 and mounted which worked but it didn’t add to the overall amount of disk space. This was because I should have umounted everything first and then run it I assume. So my question is, do I A> umount it and then run: mkfs.lustre --ost —mgsnode=172.16.16.5 --param="mdt.group_upcall=NONE" /dev/mapper/mpath7p2 and then mount or B> umount everything and then run the tunefs.lustre on everything again and then mount? everything together. A would be my choice if I could. Thanks, Alastair Ferguson IT Manager Capital Markets CRC Limited (CMCRC) Telephone: +61 2 8088 4222 Mobile: +61 424 235 159 Fax: +61 2 8088 4201 www.cmcrc.com Capital Markets CRC Ltd - Confidential Communication The information contained in this e-mail is confidential. It is intended for the addressee only. If you receive this e-mail by mistake please promptly inform us by reply e-mail and then delete the e-mail and destroy any printed copy. You must not disclose or use in any way the information in the e-mail. There is no warranty that this e-mail is error or virus free. It may be a private communication, and if so, does not represent the views of the CMCRC and its associates. If it is a private communication, care should be taken in opening it to ensure that undue offence is not given. _______________________________________________ Lustre-discuss mailing list Lustre-discuss-aLEFhgZF4x6X6Mz3xDxJMA@public.gmane.org http://lists.lustre.org/mailman/listinfo/lustre-discuss