[Lustre-discuss] Emptied OSTs not empty

Bob Ball ball at umich.edu
Mon Jun 27 06:37:11 PDT 2011

I had the same issue with Lustre 1.8.4.  Wash, rinse, repeat....  In 
other words, do the lfs_find, do the lfs_migrate, then do the find a 
second time.   That seemed to catch most everything of importance.   I 
haven't a clue why this should be the case, but it was true on every OST 
that I migrated last fall.


On 6/27/2011 6:50 AM, Thomas Roth wrote:
> Hi all,
> I am currently moving off files of a number of OSTs - some in a machine with a predicted hardware
> failure, some for decommissioning old hardware etc. I'm deactivating the OSTs on the MDS, then "lfs
> find  --obd OSTXXXX_UUID /dir" to create a list of file to migrate.
> When finished, the OST partitions are still up to 14% full! Mounting as ldiskfs, I can inspect the
> data in O/0/d??, which all seem to be valid files, text files readable, ownership and atimes
> meaningfull etc.
> Since these OSTs have been deactivated on the clients also, nobody has complained about missing files
> - although this could just mean that our users keep Terabytes of old junk they don't access any more.
> So I wonder where these files belong to or why they are not missing. There were no severe crashes of
> the system in the recent past which could have caused major memory loss of the MDT.
> Something to worry about? Global lfs_check necessary?
> Perhaps I will do some "du" runs. Users want this info anyhow, and if I just missed the files in the
> "lfs find" run, they should show up as errors here.
> Regards,
> Thomas
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss

More information about the lustre-discuss mailing list