On Tue, 2008-02-05 at 21:45 +0100, Bernd Schubert wrote:
>
>
> 1.) mkfs.lustre ... (many parameters) /dev/device
> 2.) tunefs.lustre --index={failed_index} /dev/device
>
> 3.) mount -t lustre /dev/device /mnt/somewhere
>
> --> failed: Address already in use
>
> 4.) Wrote mail and got your answer
>
> 3.) mkfs.lustre --index --writeconf ... (many paramters) /dev/device
^
You need to specify which index it should be (a numeric value).
> Now I mounted the mgs as ldiskfs, and in CONFIGS/ there is no file for the
> missing ost.
> But now I just found the reason - the failed OST was still activated on the
> clients. After deleting CONFIGS/{fsname}-client and remounting as type lustre
> again, registering the failed ost works!
> I guess one shouldn't do it this way if one still has important data on the
> filesystem ;)
Seems like you worked around it in any case. :-)
> Thanks a lot for your help,
NP. Just sorry my explanation was not more clear.
b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
