SamyGO

And.. well... it didn't work too well. After a couple of files (~190) I got a "No space left on device"-message from rar2fs. Problem: movies rar'd as .part001.rar, .part002.rar, etc.: rar2fs tries to unrar each file, even if they belong to just one movie. Hold on here. Why would rar2fs ca...

The logs look ok, there are no unexpected errors! It seems the player just gives up for Shrek after a while :( For the AVI1.0 and no video it is most probably because the player lost frame sync during playback. The logs are very clear. A common pattern seems to be that after a few or only a single r...

Ok, after spending some time on writing a complete comparison engine and generating random access patterns into the I/O stream I actually found a few exotic bugs. In the patch provided all (so far discovered) ;) bugs should be fixed. Please try it, I hope it will make a difference. Note that there a...

Try this and see if it makes any difference. I try to fill the index array with 0xff instead of 0 and the reader thread is implicitly turned off. But I do not have much hope I am afraid :( EDIT: I have now checked, double checked and triple checked the logic when jumping backwards in the stream and ...

Average of movie with picture freezing is CPU about 25% (with -f key). The only at beginning it was about 98%, but later dropped and kept stable at 22-25% level. Well, is not that much about CPU usage in general, it is more of CPU offered by the system to the reader thread. It seems it gets a lot o...

*sigh*, the log looks better, but there are still issues with the reader thread, it does not get enough CPU! Can you try again, this time without using the -f switch? That is, start rar2fs as a real daemon.
You then need to umount to release the mount point.

Try this.

Ah, yes. Did not expect any improvement. Only more logging for troubleshooting. Will get back with a new patch. Think I see what may be the problem.

Try this patch. It will do extended logging. Try the Shrek movie and also the AVI 1.0 tested last.
I will probably need to do some more patches before I can see what the real problem is, but this one should at least narrow it down a bit.

I understand. The log does not look good Definitely something I need to look into. Can not do much from where I am right now. But I will create a new patch with extended traces to try to identify what is going on. As I said, it seems there is a path in the code that I never really tested before