I would check if the file list generated by find contains those remaining (after migration) files. If yes, then there is a chance that those files were changed during migration and checksum didn't match thus they were not migrated. Also there is a chance that the migration script has a problem with parsing names of some files thus fails to transfer them. I guess you could do some debugging of the migration process and narrow down the problem.<br>
<br>Best regards<br><br>Wojciech <br><br><div class="gmail_quote">On 27 June 2011 14:37, Bob Ball <span dir="ltr"><<a href="mailto:ball@umich.edu">ball@umich.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I had the same issue with Lustre 1.8.4. Wash, rinse, repeat.... In<br>
other words, do the lfs_find, do the lfs_migrate, then do the find a<br>
second time. That seemed to catch most everything of importance. I<br>
haven't a clue why this should be the case, but it was true on every OST<br>
that I migrated last fall.<br>
<font color="#888888"><br>
bob<br>
</font><div><div></div><div class="h5"><br>
On 6/27/2011 6:50 AM, Thomas Roth wrote:<br>
> Hi all,<br>
><br>
> I am currently moving off files of a number of OSTs - some in a machine with a predicted hardware<br>
> failure, some for decommissioning old hardware etc. I'm deactivating the OSTs on the MDS, then "lfs<br>
> find --obd OSTXXXX_UUID /dir" to create a list of file to migrate.<br>
> When finished, the OST partitions are still up to 14% full! Mounting as ldiskfs, I can inspect the<br>
> data in O/0/d??, which all seem to be valid files, text files readable, ownership and atimes<br>
> meaningfull etc.<br>
> Since these OSTs have been deactivated on the clients also, nobody has complained about missing files<br>
> - although this could just mean that our users keep Terabytes of old junk they don't access any more.<br>
> So I wonder where these files belong to or why they are not missing. There were no severe crashes of<br>
> the system in the recent past which could have caused major memory loss of the MDT.<br>
> Something to worry about? Global lfs_check necessary?<br>
><br>
> Perhaps I will do some "du" runs. Users want this info anyhow, and if I just missed the files in the<br>
> "lfs find" run, they should show up as errors here.<br>
><br>
> Regards,<br>
> Thomas<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Lustre-discuss mailing list<br>
> <a href="mailto:Lustre-discuss@lists.lustre.org">Lustre-discuss@lists.lustre.org</a><br>
> <a href="http://lists.lustre.org/mailman/listinfo/lustre-discuss" target="_blank">http://lists.lustre.org/mailman/listinfo/lustre-discuss</a><br>
><br>
_______________________________________________<br>
Lustre-discuss mailing list<br>
<a href="mailto:Lustre-discuss@lists.lustre.org">Lustre-discuss@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/mailman/listinfo/lustre-discuss" target="_blank">http://lists.lustre.org/mailman/listinfo/lustre-discuss</a><br>
</div></div></blockquote></div>