First, i probably need to reassure people who were scared by my posts: no there is no risk this corruption makes your phone die. It"s just about the state of the filesystem.
So, what triggers the corruption ?
Mounting any RFS filesystem without check=no
How is the filesystem corrupted ?
There are several symptoms:
- Directory names gets CAPSED: Example: /system/bin becomes /system/BIN
- files becomes unreadable, or directories becomes unlistable
- user.log is created (seems it could be created in other situations)
I made previously an attempt of auto-detection + correction for Voodoo lagfix but didn't succeed because the filesystem errors seems to vary at each mount.
The more you write on a non-check=no mounted RFS, the more the corruption grows.
This is valid not only for /system but for any RFS.
I use a kernel which you say creates corruption but everything works! Are you a big fat lier who wants me to use Voodoo instead?
Hehe, I read that
Lots of things are strange about RFS and i hit several bugs during Voodoo 5 development, which is able to converts /system back to RFS
This is just another example of an RFS inconsistency. Why the hell should all filesystem be mounted only with -o check=no ?
Good question, this is absurd ^^
However, a RFS filesystem mounted without check=no stay usable as long as you continue to mount it without check=no. This is why sztupy and a lot of people didn't noticed it.
But I'm sure a few people had the issue after re-flashing another kernel and thought they made a mistake.
Official Samsung kernel don't boot, or boot but the /system has errors. Missing media files (sound?) or binary ? Yes, this is the cause.
Is this corruption report your personal interest ?
Yes, because it prevents migrating from an old ULF kernel to a Voodoo kernel.
But it's also the case with every other kernel except ULF based ones (not corrected in git ATM)
I lost a lot of hours because of this issue ^^
You know, it's just a bug. Needs to be corrected, that's all.
If the filesystem works fines on ULF kernels, why call this corruption?
Because it only mount properly on ULF kernels.
It does not work on every other including official Samsung ones.
Reaction of hardcore, Speedmod kernel's author:
Chill out guys. Let me try to simply the situation:
1. Supercurio found a bug with ULFK 0.3. It was probably a typo or oversight, but it results in /system not getting mounted correctly, which corrupts /system in some slow way.
2. The corruption is there, but also not that bad because it will work fine for most people. The chance of it crashing or causing immediate harm is slim. And its fixable by a new firmware flash.
3. But nevertheless, its still a bug. And its fixable, and has been fixed in ULFK scripts. I have posted the fixed ULFK scripts already, so all the ULFK kernel makers can update it.
4. Since it is a ULFK bug, it is likely that all the active ULFK kernels devs will update their kernels to fix it.
5. When that happens, users of the older ULFK kernels will run into the same problem (unable to boot) that they run into when flashing back to stock/Voodoo/other fixed kernels. They will have to either (i) use this tool or other methods to fix it, or (ii) reflash their firmware.
The point is: It's a real problem with ULFK 0.3. But it won't cause much *immediate* harm. But its been fixed anyway in newer ULFK. And eventually all ULFK users will have to update and go through the 'conversion' hassle.
Now for something non-technical. I really want to thank Supercurio for finding and sharing this problem. He didn't have to and we could just have continued to be un-informed. But he did, and even tries to make an 'easy' fix (which may not even be possible!).
I can't say the same for everyone, but if I know that there is a bug with the software, and there *is* a fix, then I'd rather implement the fix. Even though not doing so may not cause me any immediate damage. But it's really the individual person's choice.
In second post: how to correct the issue.
Big thanks to lots of people that took time to send the log helping understanding this issue during the development of Voodoo.