Hello,
I have a filesystem that went south in a fairly bad way. The
lfsck(ran in read-only mode) listed 31216 files that were 'not created'
and in the lfsck output log there were error messages about dangling
inodes and when they were all added up, they equated out to 31216
dangling inodes. The question is: Is there a way to map the dangling
inodes to the files in order to save the data?
Chad
--
Chad Kerner - [EMAIL PROTECTED]
Systems Engineer, Storage Enabling Technologies
National Center for Supercomputing Applications
http://www.ncsa.uiuc.edu/~ckerner
_______________________________________________
Lustre-discuss mailing list
[email protected]
http://lists.lustre.org/mailman/listinfo/lustre-discuss
