Yes, this machine can't access the mounted file system and caused a kernel panic when we tried to access some files, it also seems to give different and incorrect values when du or df is run on it. <br><div class="gmail_extra">
<br><br><div class="gmail_quote">On 22 November 2012 19:34, Dilger, Andreas <span dir="ltr"><<a href="mailto:andreas.dilger@intel.com" target="_blank">andreas.dilger@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On 11/22/12 10:25 AM, "Mark Field" <<a href="mailto:mnfield@gmail.com">mnfield@gmail.com</a>> wrote:<br>
<br>
>Hi,<br>
><br>
>I am currently using lustre 1.8, after a OST failure, I deactivated the<br>
>OST on the MDS and made the change permanent. If I now run lctl dl on<br>
>the client nodes all of them except one show the OST as inactive<br>
> (device 7 in the output below)<br>
><br>
><br>
> 0 UP mgc MGC10.214.4.201@o2ib 78b8432f-6331-cae7-8d75-dbaba9708056 5<br>
> 1 UP lov optstr01-clilov-ffff8103350d0400<br>
>cd18b560-e476-f55d-6df1-edcbd68c361b 4<br>
> 2 UP mdc optstr01-MDT0000-mdc-ffff8103350d0400<br>
>cd18b560-e476-f55d-6df1-edcbd68c361b 5<br>
> 3 UP osc optstr01-OST0000-osc-ffff8103350d0400<br>
>cd18b560-e476-f55d-6df1-edcbd68c361b 5<br>
> 4 UP osc optstr01-OST0001-osc-ffff8103350d0400<br>
>cd18b560-e476-f55d-6df1-edcbd68c361b 5<br>
> 5 UP osc optstr01-OST0002-osc-ffff8103350d0400<br>
>cd18b560-e476-f55d-6df1-edcbd68c361b 5<br>
> 6 UP osc optstr01-OST0003-osc-ffff8103350d0400<br>
>cd18b560-e476-f55d-6df1-edcbd68c361b 5<br>
> 7 IN osc optstr01-OST0004-osc-ffff8103350d0400<br>
>cd18b560-e476-f55d-6df1-edcbd68c361b 5<br>
> 8 UP osc optstr01-OST0008-osc-ffff8103350d0400<br>
>cd18b560-e476-f55d-6df1-edcbd68c361b 5<br>
> 9 UP osc optstr01-OST0005-osc-ffff8103350d0400<br>
>cd18b560-e476-f55d-6df1-edcbd68c361b 5<br>
><br>
><br>
><br>
>The other client is not working correctly, lctl dl looks like this<br>
><br>
><br>
> 0 UP mgc MGC10.214.4.201@o2ib 94226c2b-6914-6a92-5c6b-2a27ebff676e 5<br>
> 1 UP lov optstr01-clilov-ffff81016d482400<br>
>e7a4a072-c0db-aac9-c13f-bd4189986407 4<br>
> 2 UP mdc optstr01-MDT0000-mdc-ffff81016d482400<br>
>e7a4a072-c0db-aac9-c13f-bd4189986407 5<br>
> 3 UP osc optstr01-OST0000-osc-ffff81016d482400<br>
>e7a4a072-c0db-aac9-c13f-bd4189986407 5<br>
> 4 UP osc optstr01-OST0001-osc-ffff81016d482400<br>
>e7a4a072-c0db-aac9-c13f-bd4189986407 5<br>
> 5 UP osc optstr01-OST0002-osc-ffff81016d482400<br>
>e7a4a072-c0db-aac9-c13f-bd4189986407 5<br>
> 6 UP osc optstr01-OST0003-osc-ffff81016d482400<br>
>e7a4a072-c0db-aac9-c13f-bd4189986407 5<br>
> 7 UP osc optstr01-OST0004-osc-ffff81016d482400<br>
>e7a4a072-c0db-aac9-c13f-bd4189986407 4<br>
> 8 UP osc optstr01-OST0008-osc-ffff81016d482400<br>
>e7a4a072-c0db-aac9-c13f-bd4189986407 5<br>
> 9 UP osc optstr01-OST0005-osc-ffff81016d482400<br>
>e7a4a072-c0db-aac9-c13f-bd4189986407 5<br>
><br>
><br>
><br>
>Notice device 7 is 'UP' rather than 'IN' and also the last number on the<br>
>line is 4 not 5. I tried umount and re-mounting the client, and<br>
>rebooting, but it always comes back the same. Is there persistent<br>
> data somewhere on the client that is corrupt in someway and needs to be<br>
>deleted?<br>
<br>
</div></div>No, there is no persistent data on the clients at all. They get a new<br>
UUID each time they mount, so the servers can't even tell it is the same<br>
node from one mount to the next.<br>
<br>
Presumably this is causing a visible problem, or you wouldn't have<br>
mentioned it?<br>
<br>
Cheers, Andreas<br>
<br>
</blockquote></div><br></div>