I think I am posting in the right forum area, but here's my story.
I've been experimenting with the Pi for quite a while, currently with it being a perfectly happy Subversion server. However, I had an issue today.
It appeared that my subversion repo was corrupted. I tried repairing, but to no avail, I thought it was just the repo. I tried to restart (who knows, maybe this would solve the trick), however that was the breaking point - the Pi never got to the main shell.
dmeseg output is a whole lot of
EXT4-fs error (device mmcblk0p2): ext4_iget:3939 inode#31723: comm tput: bogus i_mode (110644)
What do I try to do? well repair the filesystem - fsck -p /dev/mmcblk0p2
it tells me that there are errors, try to repair - yes - fail.
Error storing directory block information.....memory allocation failed.
Okay, that seems odd - it shouldn't fail, as the RAM is almost free (free -h reports only about 20 mb used), but what the heck, lets try to do the fsck disk caching (http://linux.die.net/man/5/e2fsck.conf) - after I configure the disk cache, same error.
So What have I done after? tried to do repair the SD card under another Linux server I have running, and same thing as well - "Memory allocation failed".
I am starting to think that I can't bring the install back to life.
PS: It probably happened because of the turbo mode overclock, I hear that SD card corruption can happen.
If anyone has any clues as to how one would go about fixing it, please let me know,
PS: Below is the error message that I get, regardless of where I run it at (the fsck command)