what I did was restart the phone with nitdroid and then connect the phone to a computer with ubuntu linux I try to repair the errors with fsck from there. The first time I did it no problem, but after I did it again, something strange happened there and the program asked me to change certain things in the file system and I accept without realizing that damaged the file system.

i wanted to build on device using a nfs mount but it failed when installing some packages :

Preparing to replace libc6 2.5.0-1osso10 (using .../libc6_2.5.0-1osso7_armel.deb) ...
Unpacking replacement libc6 ...
dpkg: error processing /var/cache/apt/archives/libc6_2.5.0-1osso7_armel.deb (--unpack):
error setting ownership of symlink `./lib/libpthread.so.0': Stale NFS file handle
Errors were encountered while processing:
/var/cache/apt/archives/libc6_2.5.0-1osso7_armel.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I couldn't stop trying the method of forced automatically fsck at boot. The result: Phone boots up, all buttons became marked with "no image found", the menu shows just weird symbols - totally ruined. So, the only thing for rescue is reflash. But later.. USB socket is broken, first have to fix this.
I remember when I knew, OK no USB socket, no way to flash.. don't mess up anything.......

This really sucks, I get this error every day on /opt after a hard filesystem load. I doubt if my flash memory is dying, I can fix this booting via BackupMenu, exposing /opt via usb and running fsck.ext3 -fy /dev/sdX from my desktop.

BackupMenu itself fails at this point, it tells me to check fs manually.

Turning on automatic fsck on boot via kernel-power = death in two boots, it turns /opt into a piece of crap.

A research is needed on how can we manage that without usb or booting another os from sd card.

Btw, returning /proc/sys/vm/laptop_mode to 0 helped me a bit, but performance suffers.

Does this thread still reflect the options one has when hit by a stale file handle in /home/user ?
What's the best way to fix this?