Details
-
Question/Request
-
Resolution: Unresolved
-
Minor
-
None
-
Lustre 2.8.0
-
None
-
ORNL's altas files system running patched lustre 2.8.2 with same version for it clients
-
9223372036854775807
Description
Recently we suffered an outage for some of servers and after recover started a lfsck run for all the options, namespace, layout etc. During the run a large number of files ended up cached in /lustre/altas2/.lustre/lost+found/MDT0000/* as well as the MDT on the MDS server to the point it crashed the MDS since we don't have large directory support. To prevent this all zero size files are being deleted. At the same time user files that were accessible after the recovery are no longer accessible after the lfsck launch. Their data is ended up in lost+found. We are attempting to look at recovering this data but no documentation can be found easily on how to do that for lost+found files. I have looked at the sanity-lfsck for information on how to do this but their doesn't seem to be a clear answer on how to figure out the original location of the files in lost+found. We end attempted to use ll_decode_linkea but the parent return was "lost+found" itself instead of the original directory. As for sanity-lfsck none of the test actually determine the original location of such displaced files by using tools but use the path originally given when creating a test file. So we are looking for pointers on how to recover these files.