About two years ago I sold off all my BeOS hardware.
Before I got rid of everything though, I made a 4.4GB image of the disk that had all my development work / important files on it. I scp-ed the file to my iMac, and burnt the image file (as a file) on a DVD.
The idea, was that when Haiku got mature enough, and when I had a working x86 box that would be able to boot it natively, I’d mount the image on the DVD, and recover all my old stuff.
Fastforward two years – I’ve now got a laptop that will boot Haiku (beautifully!) on the raw hardware, as well as in VirtualBox. Even the wireless is working!
I pulled out that DVD today, and I’ve spent quite some time trying multiple methods of getting the data off it.
Each time, I run into what appears to be a bug with Haiku.
If I try to mount the image file with tracker, it immediate looks like a race condition, and Tracker hangs – never to be killed. Rebooting is the only way to get things back to normal.
If I try to copy the image file with tracker, it looks a lot like the linked screen shot above. Once the memory cache gets pretty full, both processors seem to get into contention (race condition in memory management?) and everything stalls.
If I try to use DD to write the image to a partition, the same thing eventually happens (although much faster).
If I use the BFSTools recover program, same thing. The cache continues to grow, then all of a sudden (after about 1024MB of data read from device) things just… stop.
This is happening on a Dell Latitude D620, 4GB of physical RAM.
Is this a bug? Does anyone have suggestions?