The table format when pasted here is hard to decipher - but it is saying (i think) for /home/opt 128k Inodes created, 17K used and 111K available (13% used).

Nokia-N900:~# df -ih
Filesystem Inodes Used Available Use% Mounted on
rootfs 0 0 0 0% /
ubi0:rootfs 0 0 0 0% /
tmpfs 28.7K 51 28.7K 0% /tmp
tmpfs 28.7K 35 28.7K 0% /var/run
none 28.7K 728 28.0K 2% /dev
tmpfs 28.7K 3 28.7K 0% /dev/shm
/dev/mmcblk0p2 128.0K 17.0K 111.0K 13% /home
/home/opt 128.0K 17.0K 111.0K 13% /opt
/opt/pymaemo/usr/lib/python2.5
128.0K 17.0K 111.0K 13% /usr/lib/python2.5
/opt/pymaemo/usr/share/pyshared
128.0K 17.0K 111.0K 13% /usr/share/pyshared
/opt/pymaemo/usr/lib/pyshared
128.0K 17.0K 111.0K 13% /usr/lib/pyshared
/opt/pymaemo/usr/share/python-support
128.0K 17.0K 111.0K 13% /usr/share/python-support
/opt/pymaemo/usr/lib/python-support
128.0K 17.0K 111.0K 13% /usr/lib/python-support
/dev/mmcblk0p1 0 0 0 0% /home/user/MyDocs
/dev/mmcblk1p1 0 0 0 0% /media/mmc1
Nokia-N900:~# for i in /*; do echo $i; find $i |wc -l; done

I used this:-
for i in /*; do echo $i; find $i |wc -l; done

to look at the /opt ones and eventually tracked down the biggest part 8.9k Inodes to /opt/../microb-engine/chrome and it seems that most of it is some sort of language files each with about 149 inodes.

/usr also was giving a large number of Inodes and the biggest was /proc with 28k Inodes.

But if my interpretation of the table is correct, it doesn't look like and inode problem.

BTW the Putty/Openssh not connecting issue was eventually solved by uninstalling openssh (client and server) and then installing them again.

I think I have found out what the problem is, based on the high resource demands on the calendar process. It part of the same MfE problem with contacts duplication, but this time is it calendar entries, some are duplicated 160x!! And they are series events so 160x every year until 2037!