On Thu, 2009-07-23 at 16:35 -0700, Mark Foster wrote: > I had a file server crash twice and each time when jfs_fsck ran it > dumped a TON of files into lost+found. > Never mind what it blew away.
Uh oh. The journal _should_ protect against fsck needing to do such a drastic thing. Something's not working as it should. > Anyway there are now about 800 directories (D???????.RCN) and 30K files > (I???????.RCN) in there with little idea about how to restore them to > the proper place. Using stat and file on them is a little bit helpful > but no sign of the original paths or filenames. Unfortunately, fsck didn't like the containing directory, which contained the path information, and blew it away. > Any ideas? Time for TSK and/or jfsrec? I'm not too familiar with those, so I can't say how helpful they might be. > Thanks. Periodic backups are always a good idea. Short of that, you could at least record the inode numbers (which is part of the file name in lost +found) by running something like "find . -print | xargs ls -i > /some_file". I'm sorry this doesn't help after the fact. Shaggy -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------------ _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
