root full connman bug SFOS 3.0.2.8
 

some terrible connman bug (new to oulanka?) is causing /var/lib/connman to fill up at an alarming rate.

mine was ~500mb (root partition is only ~2000mb), and i ran out of space and hit into all sorts of problems.

i now run this every night as root user to delete files older than a week:

Re: root full connman bug SFOS 3.0.2.8
 

Thanks for the workaround.

I 'only' had.around 90MB.
Just zipped and deleted them.

But is it really only Oulanka related?
There is a "question" on tjc but I cannot find it anymore and I believe it was already earlier...

Re: root full connman bug SFOS 3.0.2.8
 

ive never encountered this before now, and i reflashed only 1 or 2 months ago when switching to oulanka for the first time, so it SEEMS fairly new.

but no, i am not in way sure its new to oulanka. too many other variables
maybe it was fixed in the past, but regression unfixed it in oulanka? dunno.

Re: root full connman bug SFOS 3.0.2.8
 

also, `/var/lib` is just where id put my large, volatile, private, user-specific caches. truly an ideal location.

Re: root full connman bug SFOS 3.0.2.8
 

Just checked with my daughters Jolla (3.0.2.8 Oulanka), and had only about 2M. Apparently for each SSID seen (not necessarily connected) 3 files are stored (history.home.{day,hour,month}, but they take 3*24 bytes (with btfrs maybe 1M :)

I suppose you can safely delete the directories which don't contain a "settings" file in it (where e.g. the PSK password is stored).

Re: root full connman bug SFOS 3.0.2.8
 

Could cron-run this if/as necessary:

--
for d in $(find /var/lib/connman -type d -name wifi_\*); do
if [ -f "$d/settings" ]; then echo "KEEP $d"; else echo "KILL $d";
fi;
done
--

(you will have to do the obvious change from echo to rm, but want to keep the snippet safe..)

Re: root full connman bug SFOS 3.0.2.8
 

That explains that bug where devices crash if there are too many access points nearby!

Re: root full connman bug SFOS 3.0.2.8
 

I'm not sure the Jolla would crash when doing that (unless it fills up all space, that is).

I've just cleaned up the Jolla according to my snippet above. I'll take it with me this afternoon where I expect a number of WLANs to be nearby and check if they have been added (to confirm my hypothesis, but not necessarily yours.. :)

Re: root full connman bug SFOS 3.0.2.8
 

Doesn't sound too unlikely to me. Heavy i/o is a fairly common cause of kernel panics, and I presume the crashes are caused by kernel panics. However, I only understand these things on a surface level.

Re: root full connman bug SFOS 3.0.2.8
 

A kernel panic because of a few (let's say hundreds) of WiFi access points nearby causing.3x24bytes to be written?
Nah, but maybe only if all space is filled, as reinob said.

Re: root full connman bug SFOS 3.0.2.8
 

OK, in the end I didn't take with me, but if wasn't necessary. I just looked and lots of WLANs (precisely: 30) have appeared, each with the 3x24-byte files.

I guess you'd need lots (~ 7E6) of seen WLANs to fill 500MB (as OP reported). But with BTRFS and perhaps some bad optimization for small files, the actual disk space used can grow pretty fast (e.g. assuming 4Kb per file, seeing ~40000 WLANs would fill up 500MB of disk).