On Apr 04, 2009 18:58 -0400, Mag Gam wrote: > I see, so there is no easy way to recover on the MGS. I have a good > idea who the user is for these files but the file names are very hard > to decypher. They have names like 543434. I am not sure what file that > would be part of...
The problem at this point is that the directories were corrupted (unfortunately due to bug 18695 I think) and the names of the files are lost. The best that e2fsck can do at this point is to put the files into lost+found with the inode number as the filename. > On Sat, Apr 4, 2009 at 5:57 PM, Andreas Dilger <[email protected]> wrote: > > On Apr 04, 2009 09:36 -0400, Mag Gam wrote: > >> I have over 52k files in my lost+found of my MGS (not my OSTs). I am > >> not sure what tool I need to use to recover these files. Should i use > >> lfsck or ll_recover_lost_found_objs? > > > > That is only for the OSTs. Unfortunately, there is no easy way to > > recover them except by e.g. UID/GID and looking at the contents, > > which is true of local filesystems as well. > > > > I'd recommend making a lost+found directory in each user's home dir > > and then moving all of their files into their directory (with MDS > > mounted with -t ldiskfs) and let them sort it out. > > > > In Lustre 2.0 and later the MDS inodes will contain an attribute that > > holds the filename and parent directory ID that will allow recovery in > > a manner similar to how ll_recover_lost_found_objs does for the OST. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
