On 2017-03-25 09:55, Sonny Rao wrote:
> Have you looked at jfsrec ? It's helped me in the past

Currently looking, after Michael Müller suggested it. However first 
order of business was fixing the build problems (which have a ticket in 
the bug tracker for 6 years, now). And for the past weeks I've been 
duct-taping over all the bugs and crashes.

I've got it so far that it dumps out a lot of directories and files. 
However lots of these files seem to be directories that have been 
malidentified as regular files. And so far nothing solid that isn't 
total binary garbage (interestingly enough, _consistent_ binary garbage, 
like directory inodes misidentified as regular files show the same 
binary patters, although at different offsets).

Truth to be told the code quality is horrible, and it clearly shows that 
the authors' understanding of C and C++ are superficial at best (for 
example it makes absolutely no sense at all to pass const integers by 
reference) and elementary tests and protections that are mandatory when 
working on untrusted / damaged data are completely missing. As far as I 
progressed, the JFS image I'm trying to recover here is one big fuzzing 
test data set washing up all the dirty stuff.

I'll keep duct-taping around all crashes until I get it to finish 
without crashing and only then will make an assessment of how well it 
worked.


Cheers,

Wolfgang


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Jfs-discussion mailing list
Jfs-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jfs-discussion

Reply via email to