Quote:
Originally Posted by GrandpaHomer
I suppose you've used the code from 0.3.1 ... :??
The seek part of code is bugged and it's now amended in above posted version 0.3.2 :Important
We should somehow merge our current latest version, test the final product and from now on try release only the "official" version. But at least I've dusted a bit my C skills and I have now better understanding of how the program works instead of being just pure consumer of somebody's products ... :grin:
OK - I've just found out that you've actually fixed already both "length-1" and seek bugs so ... :hitw :hitw :hitw
Two more quick questions:
1. I believe that it's not necessary anymore to specify -lgmp during compile?
2. I suppose you're using dd for making the images of the disk?
|
I found the scan length bug myself and correceted in 0.4.1. It's good that we both saw it and corrected it; great minds think alike.
On the sysfs device size file, there was actually some bad char pointer arithmetic that was causing it. I had forgotten to include an extra byte for the terminating NULL character, which I changed in the 0.4.1 release. I actually came across the same problem with
Code:
/sys/block/sdf/sys/block//size
So we don't need to have hard coded device names anymore. The -h option should take care of it:
Now both bugs are fixed!
Quote:
Originally Posted by HanSooloo
Allright kids, maybe we are onto something here. I have been formatting my poor hdds with all sorts of filesystems lately and taking images of them to compare against the PS3 FS.
Well, it seems like the layout "resembles" ReiserFS. Just to show some samples here:
PS3 HDD Layout:
Code:
Start End Length
0x0B7CD000 0x0B7CDFFF 0x10000
0x16F85000 0x16F85FFF 0x10000
ReiserFS HDD Layout:
Code:
Start End Length
0x0B7CD000 0x0B7CDFFF 0x10000
0x10007E00 0x10007E0F 0x00010
0x16F85000 0x16F85FFF 0x10000
0x18007E00 0x18007E0F 0x00010
These sections are from the first occurance of a repeating section. Notice that the 0x10000 length sections start at the EXACT same address on a 60GB hdd.
Interesting thing, too, is how ReiserFS's 0x00010 section is absent in the PS3 layout. Maybe it is consolidated to the beginning of the hdd. Who knows?
The next step is to copy the same file to both PS3 and the ReiserFS formatted hdd and see where the changes are.
Keep checking back in kids...:smilew
|
Well, maybe after all we had a false alarm :-oops: It seems like I did not properly zero the hard disk before putting the ReiserFS system on it. Prior to the ReiserFS format, there were PS3 FS signatures on the disk, that resulted in the merged layout on the disk. OH WELL...
But maybe, just maybe, they are using a HUGE block size of 64K. Anyway, I am sorry if I had people's hopes up. Will try to come up with better news later.