Operation Temporarily disabled due to low memory
 

Hi, Can anyone give any direction on this error.
"Operation Temporarily Disabled due to low memory"

RootFS shows 79.1MB free
Home shows 1.3GB free
MyDocs 25.9GB free
Memory Card 0B free

Memory card has been full for months.

Started the error just this week.
Originally Home was full. I checked and found that due to the old MfE contact duplication bug, I had once again many duplicate contacts despite clearing them out in Feb this year. In some cases I had over 60 copies of the same contact.

So I deleted MfE account and it purged a good amount of memory. I added it again and once again found duplicates. I checked on the PC and despite some MS outlook bugs meaning I could see the duplicates on some searches, but could see them on others. I exported the contact file and re imported it into Outlook and this cleared all the duplicates on the PC. I added the MfE account again to the N900 and all good, no duplicate contacts.

I then discovered that the old IMAP email bug meant that I had hundreds of email from one of my IMAP accounts hogging "Home" memory. So I deleted the account which gave back more memory. Deleted the email from the IMAP server and then added the IMAP account back.

So this results in the HOME memory being mostly free as stated earlier.

So if RootFS is not full and Home is far from full, what could be causing the low memory error?

I am hoping to avoid a reflash (yet again!) as I finally managed to get DocstoGo full version working again back in February.

Re: Operation Temporarily disabled due to low memory
 

Run a
and check usage of inodes. iirc I had that once with thousands of small files using up inoodes but not filling up disk space.

Re: Operation Temporarily disabled due to low memory
 

Hi Peter, I get "df: Invalid option --i" ?

Re: Operation Temporarily disabled due to low memory
 

It is not --i
but just -i

Re: Operation Temporarily disabled due to low memory
 

Hi, Yes I typed df - ih and get the --i invalid response. I tried it directly on xterm and also via ssh (putty). same response. df -h works fine but it doesnt like -ih?

Re: Operation Temporarily disabled due to low memory
 

Nokia-N900:~# df -ih
df: invalid option -- i
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) multi-call binary

Re: Operation Temporarily disabled due to low memory
 

Strange, I am pretty sure it worked that way on N900, too (testing here with SFOS).
What about
df -i
without the h?

Re: Operation Temporarily disabled due to low memory
 

Oh, maybe.
I had always enhanced busybox installed (your output looks like default busybox)?

Have a look with

Re: Operation Temporarily disabled due to low memory
 

Yeah I think when I re-flashed this last time i ended up back on stock. Let me look at it some more. So my next question if it is Inodes , how to fix it? Just delete the files?

Re: Operation Temporarily disabled due to low memory
 

Enhanced Busybox fixed the -ih issue. Output:-

BusyBox v1.23.1 (Debian 1.23.1power2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

gainroot
Root shell enabled


BusyBox v1.23.1 (Debian 1.23.1power2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

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 52 28.7K 0% /tmp
tmpfs 28.7K 35 28.7K 0% /var/run
none 28.7K 721 28.0K 2% /dev
tmpfs 28.7K 3 28.7K 0% /dev/shm
/dev/mmcblk0p2 128.0K 13.3K 114.7K 10% /home
/home/opt 128.0K 13.3K 114.7K 10% /opt
/opt/pymaemo/usr/lib/python2.5
128.0K 13.3K 114.7K 10% /usr/lib/python2.5
/opt/pymaemo/usr/share/pyshared
128.0K 13.3K 114.7K 10% /usr/share/pyshared
/opt/pymaemo/usr/lib/pyshared
128.0K 13.3K 114.7K 10% /usr/lib/pyshared
/opt/pymaemo/usr/share/python-support
128.0K 13.3K 114.7K 10% /usr/share/python-support
/opt/pymaemo/usr/lib/python-support
128.0K 13.3K 114.7K 10% /usr/lib/python-support
/dev/mmcblk0p1 0 0 0 0% /home/user/MyDocs
/dev/mmcblk1p1 0 0 0 0% /media/mmc1
Nokia-N900:~#

Re: Operation Temporarily disabled due to low memory
 

Hi again.

So looks like Inodes are not this issue only 10%

Memory looks fine and just to be sure I freed up more RootFS space so now have 86Mb free there.

I have apt-get removed several app's to tidy it up more.

I still have the problem.

If I run the top command in xterm I see a number of resource hungry processes running after boot up. But then it seem to settle down with processes using low single digit CPU and single digit memory.

Once the error occurs again there is no apparent change in the the Top command results, it shows plenty of CPU and Memory resource available. and there are no resource hungry processes apparently runnning.

The error occurs and then it increases in frequency until it triggers a reboot.

I was connected with putty at one point and was apt-get remove tracket-cfg to make sure it wasnt a tracker-cfg issue. The error became more and more frequent and the phone rebooted and broke the putty ssh connection. I had to reboot and use xterm on the phone to finish the removal of the tracker config app. Strangely since then putty will not connect (connection refused) via ssh to the phone. Not sure if it is linked to my other issues...

Currently running a test without the SD card installed to see if there is something strange there.

Re: Operation Temporarily disabled due to low memory
 

Process PID 1666 running almost 100% of CPU and 43% memory 5 minutes after reboot. any idea what PID 1666 is ?

Re: Operation Temporarily disabled due to low memory
 

Could be anything: pids are of course allocated dynamically.
What does 'ps aux | grep 1666" say?

Re: Operation Temporarily disabled due to low memory
 

I am next t sure but afair the ext3 home partition is created with a buffer of 10% free inodes. I say not sure but as soon as I saw the output it made 'click'.
You need to find directories where a lot of small files are stored. They do not fill up space but using inodes.
Please see e.g. here: https://scoutapm.com/blog/understanding-disk-inodes
https://stackoverflow.com/questions/...mber-of-inodes

did not see the other posts but still I think you ran out of inodes on /home. 10% free does not mean they are available.

Re: Operation Temporarily disabled due to low memory
 

Hmmm, seems to be a "calendar" process.

Re: Operation Temporarily disabled due to low memory
 

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!

Re: Operation Temporarily disabled due to low memory
 

You sure have a busy calendar! :D:D

Re: Operation Temporarily disabled due to low memory
 

Yeah! Worst thing is they are now back synced to outlook, and there is no easy way to remove the duplicate entries! Just select, delete, whole series, ok each time.

I think I managed to find them all. so waiting to see if the N900 will sync and remove the duplicates seeing that they were removed on outlook. If not I will delete the MfE account and try again...

And I can check how android manages it on my other phone, as its got the same problem with duplicates now. Obviously more processing power means its not crying about it like the N900 is!

Re: Operation Temporarily disabled due to low memory
 

I am surprised that MfE even works for you on the N900 at all. The last time I used it, it synced only once a day, after my commute to work, when it switched from the mobile network to the company WiFi. Which was kind of useless: I did not need my work emails on my personal phone in the office!

(Mind you, the Exchange support in Sailfish is even worse. My last successful sync was weeks, if not months ago. I gave up and removed Exchange altogether. How can something supposedly actively maintained be worse than something abandoned years ago is beyond me.)

Re: Operation Temporarily disabled due to low memory
 

So, yes. You are definitely right about the inodes thing. Should have read the figures more proper :(

But then I do not get where this message came from?
Was disk space low? Nope.
Was/is this message really about RAM? (then it should have popped up every day for everybody ;))
Or was it 'only' low 'disk space' on /tmp (to check with a normal df -h)?

Re: Operation Temporarily disabled due to low memory
 

I had also checked with df -h and also with the top command running, none of them showed a memory problem at all. I was beginning to be concerned it was a hardware issue, but seems I was lucky it is not!

But it has definitely fixed it by clearing out the thousands of MfE duplicate calendar entries. It has been running all day yesterday and all night now and no error. The calendar process is minimal or even zero CPU% now.

And with the added benefit of RootFS being now over 87Mb free, due to housekeeping while looking for the issue.