Adrian Ulrich wrote:
> Hi Kevin,
>
>
>> But you specified that as a failover node:
>> # tunefs.lustre --erase-params
>> --param="failover.node=10.201.62...@o2ib,10.201.30...@tcp
>> failover.node=10.201.62...@o2ib,10.201.30...@tcp
>> mdt.group_upcall=/usr/sbin/l_getgroups" /dev/md10
>>
>
> Well: First i was just running
>
> # tunefs.lustre --param mdt.quota_type=ug /dev/md10
>
> and this alone was enough to break it.
>
Not sure.
>> did you specify both sets on your mkfs command line?
>>
>
> The initial installation was done / dictated by the swiss branch of
> an (no longer existing) three-letter company. This command was used
> to create the filesystem on the MDS
>
> # FS_NAME="lustre1"
> # MGS_1="10.201.62...@o2ib0,10.201.30...@tcp0"
> # MGS_2="10.201.62...@o2ib0,10.201.30...@tcp0"
> # mkfs.lustre --reformat --fsname ${FS_NAME} --mdt --mgs --failnode=${MGS_1}
> --failnode=${MGS_2} /dev/md10
>
I haven't done combined mdt/mgs for a while, so I can't recall if you
have to specify the mgs NIDs for the MDT when it is colocated with the
MGS, but I think the command should have been more like:
# mkfs.lustre --fsname ${FS_NAME} --mdt --mgs --failnode=${MGS_2}
--mgsnode=${MGS_1} --mgsnode=${MGS_2} /dev/md10
with the mkfs/first mount on MGS_1.
As I mentioned, you would not normally specify the mkfs/first-mount NIDs
as failover parameters, as they are added automatically by Lustre.
Kevin
_______________________________________________
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss
