Originally Posted by Narada2XK
~ # e2fsck -c /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
/dev/block/mmcblk0p9: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 46753, block #0, offset 0: directory corrupted
Is this supposed to happen or do I indeed have a corrupted directory?
you have a corrupted directory structure, but you don't know the reason.
This is often repairable, but...
If you have bad blocks from a MMC_CAP_ERASE brick, e2fsck will probably get stuck somewhere.
From what I read, there seem to be people having only blocks overwritten with zeros but not damaged ones.
Also, I don't really know what kind of bad blocks my phone has now, they can't be read nor written to. Each software accessing them seems to get stuck.
In general such an fsck error can only occur when the system is stopped suddenly somewhere in the middle of some kind of writing to disk or the system has a bug somewhere.
Some standard PC scenarios do not apply or should be uncommon:
- power switched off
You can't do that with the power switch. When battery is running out of power you get a warning and if you ignore this the phone finally shuts down itself in an orderly manner.
But you can indeed pull the battery, so beware, don't do this if you don't need to and always wait some minute or two.
- system crash, blue screen etc.
I never saw something like this on android, did you?
Linux is generally very stable and most instabilities have to do with crappy PC hardware or undocumented hardware interfaces etc. Android hardware seems to be designed much cleaner.
But there are also some critical items: overclocking or undervolting if not tested thoroughly, patching and tweaking kernels and root apps accessing hardware or disks may lead to disk failures too.