Hi
Since ever I noticed a weird thing on XMP: /cache partition is always almost empty.
Yes, I checked many times during a long time, it's like is never used.
Code:
$ df
/cache 101.5M 1.1M 100.4M 4096
I have only an empty lost+found dir and two files under recovery dir:
Code:
# ls
-rw-r--r-- root root 105 2012-12-15 02:07 last_install
-rw-r----- root root 3214 2012-12-22 10:36 last_log
For example, in a previous phone /cache was actively used by market for downloading packages before installing them.
Here on XMP I can't upgrade also small packages (40+ megs free on /data) 'cause they're downloaded in /data and fill it before being upgraded, and /cache remains always empty.
In addition, if for some reason playstore crashes while downloading a big app (30megs+), it leaves my /data (almost)full and I must remove by hand a large temporary file from /data/system.
Well, /data is used instead of /cache, 100mb wasted in this way.
Someone else finds experiences the same behaviour?
I was thinking about a linking trick to use that space (for dalvick or swap...), but I'd prefer it would be correctly used by system.
Infos: SK17i, stock .587, root, locked BL, link2sd.
Thanks, bye.
Same in Xperia Mini
Well, this isn't nice...
some ideas
Hello! I was doing several searches and come to some results:
Note: I will not try it on my phone (Xperia Mini Pro) because I'm still an apprentice to flash and modify it, and secondly I have no resources to change my phone if something goes wrong. Finally, sorry for the grammatical errors, I do not speak English natively.
The following are links taken from different forums / blogs (neither is my property).
The general idea is the same, use parted (or any similar app) to edit the partitions inside the phone.
One of the problems that arise and I have doubts about is, what is the file system of internal partitions? ext3?. is something that I have to keep reading.
This is the first blog I found where it gives a possible procedure to follow:
http://aarondiep.blogspot.com.ar/2011/11/resize-partition-on-android.html
Here's a post where one of the users that modify his partitions and, later, returned to stock status.
http://www.droidforums.net/forum/htc-droid-eris/78650-internal-storage-partitions-screwed-up.html
Here is a guide on how you use parted (includes screenshots) BUT IT DOES WITH THE SD CARD
http://mobilecon.info/how-to-partition-sdcard-using-parted-partition.html
Finally, a tool for YAFFS2 file system:
http://forum.xda-developers.com/showthread.php?t=1645412
I hope these links are useful. I really would like to use optimally all the hardware of the phone.
Exitos!! :laugh:
Hi!
Thanks for your interest!
Resizing partitions, I read time ago, is a really critical operation.
I expect to have /cache partition as it has been made, the problem is that apps do not use it!
Resizing that block device to, let's say, zero, would give space to other partitions, but we'd lack a cache.
I definitely believe one of master questions is: where the hell does playstore download packages before installing?
During a big upgrade (let's say angry birds Rio 30+ megs) with df I only see /data growing (and /cache always empty), but after a lot of searching for newest and biggest files (busybox ls -ltrh, busybox ls -Shl) I could not find where they are put.
Once found this download location (no, it's not /data/data/com.android.vending/cache/main), would be easy to bind /cache to this dir.
Apk files from Google Play is downloaded to: data/data/com.android.providers.downloads/cache/
Wysyłane z mojego SK17i za pomocą Tapatalk 2
Hi
Many thanks for this tip!
Well, it's true apk are downloaded there.
BUT I see a strange behaviour: when I recieve the "low memory" (space on /data partition) notification, the apk suddenly disappears! :what:
In logs I see a lot of "couldn't openat chache: no such file or directory" immediately before low space notification log line...
You can use cache as swap if your kernel support it..
Sent from my Walkie'Talkie
Hi
Well, i symlinked /data/data/com.android.providers.downloads/cache to /cache/cache, and the partition is now correctly used by play store.
Is really strange that this is not a system default, btw.
EDIT: the /cache/cache was regularly erased by system, I symlinked /data/data/com.android.providers.downloads/cache to /cache and all is ok now.
EDIT2: you must previously remove (rmdir) the existing /data/data/com.android.providers.downloads/cache!
Could you put the exact command?
luchoz said:
Could you put the exact command?
Click to expand...
Click to collapse
Code:
ln -s /data/data/com.android.providers.downloads/cache /cache
:good:
thank you!!
would use XD
New info!!
http://forum.xda-developers.com/showthread.php?t=1959691
Really interesting
Related
Confirmed by droopypillow -Thanks
This fix is NOT just for the market not downloading apps issue, it actually was bugging me quite a lot that none of my apps were attached to the market so I had to use alternative methods, like app brain or an app updater app to know when I could update my apps
HebrewToYou was kind enough to tell us how to fix only the part where the market won't download apps if you have 1.5 cache set in your custom MTD partitions. So either do this or resize your cache to like 60 as recommended by the helpful fellow aaldiar
HebrewToYou said:
So here's an *actual* fix that doesn't involve replacing the Market app...
...it appears this issue may be localized to people with custom MTD partitions.
Thanks go out to JTownBrewer and FredBo (on #mytouchslide @ freenode IRC) for figuring this out:
Open up your favorite terminal emulator -- I like Better Terminal Emulator Pro -- and enter...
Code:
su
cp -a /dev/cache/download /data/cache
Market apps will once again be downloading properly. This *may* not work after rebooting, so just keep that in mind.
Click to expand...
Click to collapse
What this fixes
Apps not being attached to the market
(Make sense since I have Custom MTD partitions) HebrewToYou tells me that only for users with custom MTD partitions: Not being able to download apps (since build 20)
The Only Requirement
Must have ADB.exe and must know how to get to it through command prompt, my steps are simple enough that that is the only thing you need to know.
Windows Instructions I guess, not so sure how different on Mac or Linux
Download the Vending.apk I attached at the bottem
Put Vending.apk in the folder where adb.exe is located
Go to folder where adb.exe is located with command prompt
This may or may not be unnecessary, but force close and clear you cache on the Market app. It's what I did so just in case, k?
On your phone either go into recovery, or if you have S-Off I think you can type
Code:
adb shell
mount -o rw,remount /system
exit
and you should be able to push to /system without a problem, may be unnecessary but I always do it so I had to add that part
Then in your command prompt type
Code:
adb push Vending.apk /system/app
Open your Marketplace now and see if it's working.
What I did is I took the Vending.apk from the cm6 g-apps, I assure you it works perfect except it is an older version of the marketplace, so maybe it even has the 24 hours for a refund still? I'm not sure and I don't really feel like checking. My phone hasn't tried to update the marketplace so it I've been using this fine for the past 2 days when I first noticed my market wasn't working but at the time I thought it was just me because of a few issues I caused myself
RESERVED to include additional info about what build this error is fixed on when Cyanogen fixes this issue for all devices
All I did for my market to work was download the same file 5 times.. it wouldn't install.. then reboot the phone, try to download apps again like 2 more tries and now market works for me.
Gj on the app too
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
xaodxkevin said:
If you're good with ADB: For anyone who's got a bit of expertise with adb and whatnot, please post if there are any errors in this post and what should be different for I am sick and there may be errors. Seriously though I really need some sleep, good night.
I cannot stress this enough!Please read comments before doing this, there may be an error in my post =\ and hopefully someone's posted the correction or confirmed that this works 100%
I'm really sick, but I felt this could help many people so I'm posting this anyways hoping I don't make any errors and I really don't feel like making this look very nice right now but heres a temp fix
The Only Requirement
Must have ADB.exe and must know how to get to it through command prompt, my steps are simple enough that that is the only thing you need to know.
What this fixes
Not being able to download apps (since build 20?)
And apps not being attached to the market
Windows Instructions I guess, not so sure how different on Mac or Linux
Download the Vending.apk I attached at the bottem
Put Vending.apk in the folder where adb.exe is located
Go to folder where adb.exe is located with command prompt
This may or may not be unnecessary, but force close and clear you cache on the Market app. It's what I did so just in case, k?
On your phone either go into recovery, or if you have S-Off I think you can type
Code:
adb shell
mount -o rw,remount /system
exit
and you should be able to push to /system without a problem, may be unnecessary but I always do it so I had to add that part
Then in your command prompt type
Code:
adb push Vending.apk /system/app
Open your Marketplace now and see if it's working.
What I did is I took the Vending.apk from the cm6 g-apps, I assure you it works perfect except it is an older version of the marketplace, so maybe it even has the 24 hours for a refund still? I'm not sure and I don't really feel like checking. My phone hasn't tried to update the marketplace so it I've been using this fine for the past 2 days when I first noticed my market wasn't working but at the time I thought it was just me because of a few issues I caused myself
p.s.
If this is in the wrong location, move it please? I wasn't too sure where to put this
+
if there are any errors here please post? seriously I'm really sick and this took every ounce of energy and concentration I had so there may be a mistake somewhere and yes I've proof read it about 100x now >:|
Click to expand...
Click to collapse
ive market downloading issues since build 20..i did everything step by step except step 4..and now my market works...thanks for the temporary fix
So here's an *actual* fix that doesn't involve replacing the Market app...
...it appears this issue may be localized to people with custom MTD partitions.
Thanks go out to JTownBrewer and FredBo (on #mytouchslide @ freenode IRC) for figuring this out:
Open up your favorite terminal emulator -- I like Better Terminal Emulator Pro -- and enter...
Code:
su
cp -a /dev/cache/download /data/cache
Market apps will once again be downloading properly. This *may* not work after rebooting, so just keep that in mind.
Thanks for confirming droopypillow
And
Thanks HebrewToYou for the fix once I get home I'll add note of it and credit you, but I still prefer this one because it keeps my apps attached to the market. I'm not sure exactly who/why people are getting that issue but I'll definitely be happy with the old market until I hear that's fixed.
I flashed build 26 market is working again on this build for me..
Sent from my T-Mobile myTouch 3G Slide using XDA App
I have the custom MTD partitions and simply changed the cache from 1.5 to 60 and that solved my Market and GPS problems instantly. Just an FYI for you guys.
aaldiar said:
I have the custom MTD partitions and simply changed the cache from 1.5 to 60 and that solved my Market and GPS problems instantly. Just an FYI for you guys.
Click to expand...
Click to collapse
so the cache was also causing the GPS problems? Thanks, I'll make sure to change the cache size immediately
I'll continue using this though until the apps being attached to market issue is fixed
xaodxkevin said:
so the cache was also causing the GPS problems? Thanks, I'll make sure to change the cache size immediately
I'll continue using this though until the apps being attached to market issue is fixed
Click to expand...
Click to collapse
I have a 1.5meg cache and have no issues with gps...I had market problems from. Build 20-25..but I did nothing wxcept flash build 26 and it is fixed..
Sent from my T-Mobile myTouch 3G Slide using XDA App
Yeah, I don't think the cache partition size has anything to do with GPS issues. This was purely a fix for the market.
Lol, I know it is a fix for the market. But I still had GPS issues with 26 along with market problems. Might just be some hardware dealio with my particular slide series or something. All I know is once I did the partition my GPS and market worked instantly.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I'm on nightly #27, no market issues. Custom mtd with cache @ 1.5 as well.
How do I see what the cache size is and change it?
(Sorry for the noob question).
Please see this thread: http://forum.xda-developers.com/showthread.php?t=893706
i am running custom mtd and notice for some reason something keeps remounting my /sd-ext and /cache partition to RO which causes the failure. Rebooting and updating/installing the apps right away usually works but it's only a matter of time before it gets remount as RO. Also adb shell will not allow me to remount it back to RW, it doesn't give me any errors using mount but it just stays at RO.
right after a reboot:
Code:
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext3 (rw,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
/dev/block/mtdblock4 on /dev/cache type yaffs2 (rw,nosuid,nodev)
after running:
Code:
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /sd-ext type ext3 (ro,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext3 (ro,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
/dev/block/mtdblock4 on /dev/cache type yaffs2 (rw,nosuid,nodev)
*edit* failed again
Hi
Sorry for absolutely-n00b-liking question, but is the utility of /cache partition??
It's 100megs big, and it's ALWAYS empty.
In past I controlled with "df", also when downloading apps from play store it's fully empty.
Really looks like 100megs wasted...
Someone could please clarify this?
Thansk you, bye.
Hi! First of all /cache is essential part of Android OS. It really seems absolute empty, but it stored temporary files. Andoid have very complex cache system. For example instead of closing app, Android caches it and put it on /cache partition for quick restart in the future and RAM salvage
Hi
In my previous (stolen :crying phone, /cache was really used, and sometimes filled...
I'll try with a simple script running in background, like "while 1; df /cache >> /sdcard/cachelog.txt; sleep 3" to monitor it's usage.
Thanks for your answer.
Bye.
Hello everybody, I'm Dejan and I could use some help please.
I have Samsung Galaxy SII GT 9100 with broken screen and I have some very important stuff in it. Screen is totally broken and I cant see a thing. Long story short i used Fuzzy Meep's app but I'm stuck deep in the mud so thats off. I booted phone in my custom recovery , installed ADB on PC and managed to connect to the device. But I can't make my way thru the sdcard. Here is what I did:
G:\ADB>adb.exe shell
~ # cd etc
cd etc
/etc # ls
ls
recovery.fstab
/etc # cat recovery.fstab
cat recovery.fstab
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options
> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime
wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,j
ournal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,j
ournal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,d
iscard,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,j
ournal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0 auto auto defaults voldmanaged=sdcard0:
11,nonremovable,noemulatedsd
/devices/platform/s3c-sdhci.2/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:
auto
/devices/platform/s3c_otghcd/usb auto auto defaults voldmanaged=usbdisk0
:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recovery
only
/dev/block/mmcblk0p6 /recovery emmc defaults recovery
only
How do i mount internal memory and pull out my data? Any help is appreciated. Thanks
It's a CM LInaro Kitkat 4.4.2 with custom kernel. With older versions of Android I was able to do what I was attempting to do but I've read somewhere about certain change when mounting storage on 4.4.2.
Thanks in advance.
Noone? Reallu? At least some info about device reading out data directly from the storage chip?
denkodenko said:
Noone? Reallu? At least some info about device reading out data directly from the storage chip?
Click to expand...
Click to collapse
That isn't even remotely possible for an end user. The only people who might be able to do that is a company which specialises in recovery of data from dead HDDs'. If it is possible, expect it to be very very expensive. I've never seen a single person post here in 2.5 yrs saying they've had this done successfully. Even if this is was possible, fixing your screen would be cheaper.
Very few people here have attempted to do what you're doing with ADB (me included; frankly, if the data was that important to me, I'd pay $120 for a new screen to save myself hassles, but I wouldn't be in that situation to begin with because I back stuff up). Unfortunately, you're going to be in for a rather long wait if you don't manage to work this out on your own, many people who may have been able to help you don't post here anymore, they've moved onto other phones given it's been 3 yrs since this phone was released.
MistahBungle said:
That isn't even remotely possible for an end user. The only people who might be able to do that is a company which specialises in recovery of data from dead HDDs'. If it is possible, expect it to be very very expensive. I've never seen a single person post here in 2.5 yrs saying they've had this done successfully. Even if this is was possible, fixing your screen would be cheaper.
Very few people here have attempted to do what you're doing with ADB (me included; frankly, if the data was that important to me, I'd pay $120 for a new screen to save myself hassles, but I wouldn't be in that situation to begin with because I back stuff up). Unfortunately, you're going to be in for a rather long wait if you don't manage to work this out on your own, many people who may have been able to help you don't post here anymore, they've moved onto other phones given it's been 3 yrs since this phone was released.
Click to expand...
Click to collapse
Well at least I gave it a shot but yeah... you are probably right I shouldn't have bothered posting and I was pretty sure someone somewhere might have asked the exact same question unfortunately I couldn't find it. I know how annoying these questions can be and I'm very sorry if I made someone angry. Long story short - I managed to get my pictures and videos back, as well as contacts. I do back those stuff up. however I had some .bin files for work that I lost but I've been living with that. It just might take some time browsing on the Internet finding them again but I'd rather do that than trying to do anything with the phone. I bought it $100 last year, the screen alone is that much, there's no point in fixing it. And at last but not least, thanksfor the reply.
Nah, they're not annoying It's just a very unusual situation, and as I said, if you want help with that sort of stuff with this phone on here, because so many people have moved on, you need to be really patient, that's all.
Same story
Shortly broken display no touch input. I had custom KitKat rom.
I had almost given up trying to mount the internal sd card with ADB, following numerios forum post instructions
here is my solution using windows pc and ADB
I rebooted in recovery (I think it was 6,0xx)
Using command prompt (you also need adb.exe) :
adb remount
adb root
adb usb
Those 3 command somehow mounted the internal storage and I was able to use the "adb pull" comand to copy the whole internal sd card to my hard drive
After that I went with "adb shell" to check how the sd card was mounted and here is what I found:
"
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noe
xec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/mmcblk0p11 on /emmc type vfat (rw,dirsync,relatime,uid=1023,gid=1023,
fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortn
ame=mixed,utf8,errors=remount-ro)
"
Okay so here it goes. I had missing IMEI problem in a custom ROM when not on a samsung base. I had a neatefs (app on android) backup which I tried to restore using HC ktool (Bad idea, I know). It gives me a successfully done message and tells me to reboot. Now my phone is stuck in bootloop no matter what (Stock firmware, wipe data, factory reset nothing works) and the recovery gives the error mentioned in the title.
/efs is unmountable for me. I tried various methods mentioned for S3 and Note such as connecting the phone in ADB mode and following the steps but none of that works.
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
AKAndrew41 said:
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
Click to expand...
Click to collapse
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
ruleh said:
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
I've tried all that, none helps. I've even installed a busybox as mentioned somewhere else which said that the syntax mke2fs is not available without a busybox. Nothing worked. Still unable to mount efs afterwards.
pHraiL^ said:
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
Click to expand...
Click to collapse
I'm pretty sure it won't damage anything, or at least to me didn't. Because whenever I want to reinstall a new ROM I always format everything I've mentioned earlier so I don't find it harmful for the device, as long as you don't have data worth backing up.
Also, wipe dalvik.
If you installed busybox, make sure you uninstall the previous version prin pressing uninstall, and them installing 1.23.1 because for me sometimes it says it's intalled, but after reboot I still have the old one.
After you do that, connect phone to PC and try running
adb shell
Once you do that, give a try to the command
umount -f /efs
even if it says it's umounted, then type
mount /dev/block/mmcblk0p3 /efs
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
Click to expand...
Click to collapse
These two are the commands everyone is talking about the S3 phone having same issue. I tried everything. The first command works and it shows something like:
"The filesystem will be automatically checked every 35 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override."
For the second line of code when I try, this is what I get:
"It says "mount: can´t find /dev/block/mmcblk0p3 in /etc/fstab"
Now I have also tried adding space and /efs to the second command. It gives me nothing, not even any error. So I presume it works but then when I reboot efs is still messed up. I have no idea what these commands does actually. I think it has something related to re partitioning. Shouldn't the second command line give the same output as the first one? Its been a whole day searching for this thing. I got my phone messed up real bad.
EDIT: One more thing, when I hit the # df command on ADB, it shows 3 drives (/dev, /cache, /emmc) when not in su and 4 when in su (/dev, /cache, /emmc, /system). No where it shows any efs partition. Is there suppose to be any?
EDIT2: After the second line command. Using mount -t following someone's guide I get the efs partition but I think it is way too small. See the attachment. This partition is gone again after reboot.
OH GOD I got it working. After more searching, I found out the the block used for efs storage in S2 is mmcblk0p1 not mmcblk0p3. Phew!
Follow the same commands to make it work. Just rename the block.
Here is a guide which helped me figure out the block: http://www.usoftsmartphone.com/t306464.html
Thanks everyone
im having same trouble now with the S7. the page you share not there anymore. please share me how to figure out the block
This may be a little complicated but here is the basic gist:
1. Android 2.1 (B&N Nook Simple Touch)
2. I backup the dictionary files in /system/media/reference and then delete the originals. This shows a corresponding increase in the available space in /system
3. I create a symlink to alternate dictionary files in /sdcard/Dictionary (or /data/media/B&N Downloads/Dictionary--same result either way)
4. After rebooting I have access to new dictionary. Then I change my mind and want a different dictionary.
5. I delete the symlinks in /system/media/reference
6. I create new symlinks to a different dictionary, reboot, etc.
7. Now I get tired of all this and want to return to the stock dictionary.
8. I delete the symlinks in /system/media/reference and prepare to copy the stock backups to their original location.
BUT
9. I see that there is no longer enough space on /system to restore the original files! As an example, the stock available space in /system is 55906 kb (80% full--that's with the dictionary files in their normal place). After a few symlink cycles it may drop down to something like 30359 kb (89% full). Restoration of the stock dictionary requires about 57000 kb available space.
Blah-blah-blah. I've done this many times now, each time searching diligently for what is taking up the space that should be free. The only way to get the space back is to restore an earlier nandroid backup.
Surely this is not supposed to happen with symlinks? To delete one I am using adb shell rm. Is there something else I should be doing?
Why does the use of symlinks in /system gradually erode available space?
I am working on a routine for swapping dictionaries on an e-reader (Nook Simple Touch--Android 2.1). I've got the shell commands nailed down and have constructed an app using Tasker. It all works g...
android.stackexchange.com
Yep, and I did see your comment which turned out to be really helpful, @alecxs! I've solved the problem and answered my own question over at Stack Exchange.
The key is to kill the background process which is holding on to the dictionary databases before doing any file manipulations. If that is done, everything works as it should and no funny /system storage losses.
Thanks so much for nudging me in the right direction.
don't thank me, I had something different in mind. but yes, reading your answer remind me some strange behavior in 5 years old backup script:
after lazy umount + rm -rf /data still there was ~1GB disk space occupied.
this is because deleted files remain open for running processes, just the inode becomes orphaned.
killing system_server immediately freed up these 1GB and solved for me. lsof is your friend