from CWM recovery, check your partitions for corrupted filesystem using the e2fsck utility (information here http://www.openfsg.com/index.php/Usi...e_System_Check) from adb shell.
adb shell e2fsck -n -f -v /dev/block/mmcblk0p9 (to check /system)
adb shell e2fsck -n -f -v /dev/block/mmcblk0p10 (to check /data)
If you start to see an endless flowing river of words, wait for it to end (it might take minutes) and then read:
I'm getting lots of multiply-claimed blocks, blocks shared among two or more files, after a CLEAN installation of many Rootbox 4.2.2 versions (i tried latest official and sabermod, Nico's 60), and Resurrection Remix 4.2.2
Steps to reproduce the problem: clean install latest Rootbox/Resurrection Remix, configure a bit the rom, play with it, INSTALL some apps from playstore, update some system apps. Then, REBOOT the phone. Play with it again if you wish and eventually go to recovery.
Even if you switched to another kernel (like Dorimanx) at some point, do the check as you might have problems (unless you have flashed the kernel right after the rom, without rebooting)
I'm just a simple user but i think the problem is related to default CM10.1 kernel ((usually CWM 6.0.3.x)
Possible (common) big problem related to corrupted filesystem: phone stuck at boot/kernel logo sooner or later, after a simple switch off or reboot.
Other problems: app errors
I'm not getting those errors with clean install of KitKat 4.4.2 roms.
Please, tell me if this is a wide-spread bug, and if you can, try to reproduce yourself the steps.