Peter, Unfortunately, the reason the files are put in lost+found is that fsck could not salvage the directory containing the files, and without the parent directory, there is no file name. About the only thing to do is to examine the contents of the files and try to figure it out yourself.
Peter Weilbacher wrote: > Hi, > > we had a fs hang today with a fairly old JFS-1.0.3 on Linux-2.4.9, > so I think this may be fixed. (An ls in a directory never ended and > could not be killed with -9, while the logs show some > "jfs_read_inode: diRead failure! rc = 116" entries). > > But I wanted to ask, if you can point me a procedure how to get back > the filename of all the files he moved to /lost+found during the > following fsck. It should be possible somehow using xchklog or the > other tools, but xchklog only returns that the superblock is OK... > > Greetings, > Peter. -- David Kleikamp IBM Linux Technology Center _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
