[Lustre-discuss] OST not mounting after restore
Bernd Schubert
bs_lists at aakef.fastmail.fm
Fri Aug 27 17:00:00 PDT 2010
On Thursday, August 26, 2010, Sebastian Gutierrez wrote:
> I am in the process of upgrading one of my filesystems. I had a few older
> OSSs that I am in the process of swapping out for new disks.
>
> What I have done so far.
>
> 1. moved most of the data off of the older OSTs.
> 2. backed up the remaining files and configs on the old OSTs. Using the
> modified tar binary. 3. swapped disks created the new raid and formatted
> them.
> 4. Restored the backup to the new disks.
>
> However now I cannot mount the filesystem. I get the following message on
> the MDS.
>
> LustreError: 13b-9: lustre-OST0000 claims to have registered, but this MGS
> does not know about it, preventing registration.
>
> On the OSS I see the following messages.
>
> kernel: LustreError: 11-0: an error occurred while communicating with
> 192.168.136.10 at tcp. The mgs_target_reg operation failed with -2 kernel:
> LustreError: 27428:0:(obd_mount.c:1139:server_start_targets()) no server
> named lustre-OST0000 was started kernel: LustreError:
What does the MGS say?
> I was thinking I needed to do something like the following.
>
> perform a writeconf on all devices
> then remount the filesystem but did want to verify that this was headed in
> the right direction.
Yes, likely to be correct, but please check first what the MGS complains
about.
Cheers,
Bernd
--
Bernd Schubert
DataDirect Networks
More information about the lustre-discuss
mailing list