Hi,
Having a look at internal partitions which look like this:
Code:
# busybox df -h
Filesystem Size Used Available Use% Mounted on
[B]tmpfs 209.3M 24.0K 209.3M 0% /dev[/B]
/dev/block/mtdblock1 190.0M 179.1M 10.9M 94% /system
/dev/block/mtdblock9 199.5M 73.1M 126.4M 37% /data
/dev/block/mtdblock3 2.8M 776.0K 2.0M 28% /lgdrm
tmpfs 209.3M 0 209.3M 0% /mnt/asec
/dev/block/mtdblock8 64.0M 1.1M 62.9M 2% /cache
/dev/block/vold/179:1 3.8G 3.3G 462.8M 88% /mnt/sdcard
/dev/block/vold/179:1 3.8G 3.3G 462.8M 88% /mnt/secure/asec
I am slightly confused on this one:
Code:
tmpfs 209.3M 24.0K 209.3M 0% /dev
And this doesn't seem to total up. 190 + 199.5 + 2.8 + 64 = 456.3M
What is this 209.3M ?
Another question: Is there a way to mount /data/dalvik-cache permanently in /cache.
As one can see:
Code:
# busybox du -h /data/dalvik-cache
42.9M /data/dalvik-cache
This is growing with installed apps.
I learnt, a userinit.sh way, But is it possible to do it on the stock rooted ROM ?
i also wish to know the answer to the question.
first time android user on LG Optimus One (P500)
Related
Hey all,
Decided to downgrade from Modaco 2.3 to 2.2 as it was a little faster. Thought I would sort out the App2SD side of things too. I copied all of my SD card data off, then followed this guide:
http://android.modaco.com/content/htc-hero-hero-modaco-com/293461/how-to-partition-sdcard/
Once done I copied the SD contents back on and then downgraded to the 2.2 ROM. All back up and running but not sure if the apps have moved over as I expected them to do, is there a way to check? Otherwise what do I need to do to move them over to the SD?
Thanks
Russ
you don't need a2sd on hero.. it was only needed on g1 because of the low memory of 85 mb for apps..
hi roakes, there is already a thread that covers this:
http://forum.xda-developers.com/showthread.php?t=564932
you should have posted this in Q&A NOT Dev!!
The following post does not belong to me. I forgot who post it so all credits go to him/her:
To confirm whether A2SD is working properly from a terminal / ADB Shell type:
busybox df -h
You should see something along these lines below:
/dev/block/mccblk0p2 532.9M 67.1M 438.7M 13% /system/sd
The key is that you see one of the entries as /system/sd
This means that the phone is picked up your Ext2 partition.
Next if you see the above you can check that you setup the symlinks properly.
To do this type these cmds:
cd /data/app
pwd
The terminal returns /system/sd/app which means that the apps are now being saved onto the Ext2 Partition since the /system/sd = your Ext2 partition.
If it returns /data/app then the apps are still being installed onto the phone's internal rom.
Hope this helps, let me know if not.
Click to expand...
Click to collapse
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
/dev/block/mtdblock4 130.0M 1.3M 128.7M 1% /cache
That's what I am getting hmmmm doesnt look promising, but the partitions seem ok...
Number Start End Size Type File system Flags
1 512B 7425MB 7425MB primary fat32 lba
2 7425MB 7937MB 512MB primary ext3
3 7937MB 7969MB 32.0MB primary linux-swap(v1)
roakes said:
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
/dev/block/mtdblock4 130.0M 1.3M 128.7M 1% /cache
That's what I am getting hmmmm doesnt look promising, but the partitions seem ok...
Number Start End Size Type File system Flags
1 512B 7425MB 7425MB primary fat32 lba
2 7425MB 7937MB 512MB primary ext3
3 7937MB 7969MB 32.0MB primary linux-swap(v1)
Click to expand...
Click to collapse
Can anyone verify that this looks right?
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\DamianV>adb shell
* daemon not running. starting it now *
* daemon started successfully *
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 149.9M 20.1M 88% /system
/dev/block/mtdblock5 165.8M 22.5M 143.3M 14% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 446.9M 8.0M 415.0M 2% /system/sd
/dev/block//vold/179:1
3.3G 94.5M 3.2G 3% /sdcard
#
roakes said:
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
/dev/block/mtdblock4 130.0M 1.3M 128.7M 1% /cache
That's what I am getting hmmmm doesnt look promising, but the partitions seem ok...
Number Start End Size Type File system Flags
1 512B 7425MB 7425MB primary fat32 lba
2 7425MB 7937MB 512MB primary ext3
3 7937MB 7969MB 32.0MB primary linux-swap(v1)
Click to expand...
Click to collapse
Can anyone verify that this looks right?
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\>adb shell
* daemon not running. starting it now *
* daemon started successfully *
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 149.9M 20.1M 88% /system
/dev/block/mtdblock5 165.8M 22.5M 143.3M 14% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 446.9M 8.0M 415.0M 2% /system/sd
/dev/block//vold/179:1
3.3G 94.5M 3.2G 3% /sdcard
#
If you type:
cd /data/app
pwd
and it becomes this: /system/sd/app
Then it should be correct.
hi,
i am not sure what i am doing wrong here, I am using pinky's ROM and I have the default and used ROM manager to partition the SD card to a 512 MB ext3 and the remainder 14 GB as FAT32.
I have set the EXT4 module is enabled and App2SD is set to external.
But I still cant get the apps to install to SD, using the method above to check it. The Ext3 partition is being seen, but the symlinks are correct.
Any ideas?
Heres a dump from my CMD prompt
C:\android\tools>adb shell
sh-3.2# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 207.6M 0 207.6M 0% /dev
tmpfs 207.6M 0 207.6M 0% /mnt/asec
/dev/block/mtdblock3 250.0M 181.6M 68.4M 73% /system
/dev/block/mtdblock5 147.6M 12.0M 135.6M 8% /data
/dev/block/mtdblock4 40.0M 1.1M 38.9M 3% /cache
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block/mtdblock5 147.6M 12.0M 135.6M 8% /system/mnt/data
/dev/block/mmcblk0p2 457.4M 70.1M 362.9M 16% /system/sd
/dev/block/vold/179:1
14.6G 158.4M 14.5G 1% /mnt/sdcard
/dev/block/vold/179:1
14.6G 158.4M 14.5G 1% /mnt/secure/asec
sh-3.2# cd /data/app
cd /data/app
sh-3.2# pwd
pwd
/data/app
Hello
I'm from Brazil and I have an X850 (racer) TIM. After I sent a defective unit and returned to service with version 2.2 Froyo.
I did dowgrade of Gen2 Gen1, I installed version 2.3.4. After dowgrade did not work and the 3G market does dowload apps. I tried reinstalling everything, but this error appears in clokwork.:
"e: error in cache: recovery / log (in the space left on device)"
I can not go back to the 2.2 tim .... the error during the process offline updater (downgrade) ...
I used all the features of ClockworkMod recovery, but could not solve the problem.s ....
I believe it is possible to resolve via ADB or terminal, but do not know exactly how, percise help ...
Sorry for bad English.
google translator.
adb shell
* daemon not running. starting it now *
* daemon started successfully *
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 83312 32 83280 0% /dev
tmpfs 83312 0 83312 0% /mnt/asec
tmpfs 83312 0 83312 0% /mnt/obb
/dev/block/mtdblock4 153600 131784 21816 86% /system
/dev/block/mtdblock5 302976 51260 251716 17% /data
/dev/block/mtdblock3 12800 12800 0 100% /cache
/dev/block/vold/179:1
3487276 265464 3221812 8% /mnt/sdcard
/dev/block/vold/179:1
3487276 265464 3221812 8% /mnt/secure/asec
#
Please Help me.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi.. I have a Nexus one.. tried cyanogen7 with cw ROM, but now its in Boot loop
when checked with df -h in adb shell gave following results:
C:\>adb shell
# df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 202.8M 32.0K 202.7M 0% /dev
tmpfs 202.8M 0 202.8M 0% /mnt/asec
tmpfs 202.8M 0 202.8M 0% /mnt/obb
/dev/block/mtdblock3 145.0M 124.9M 20.1M 86% /system
/dev/block/mtdblock5 196.3M 196.3M 0 100% /data
/dev/block/mtdblock4 95.0M 16.9M 78.1M 18% /cache
/dev/block/mmcblk0p2 480.6M 8.0M 472.6M 2% /sd-ext
#
I tried clearing storage from bootloader, tried factory reset, tried format /data but no gain.
Any help please...
I'm running stock NC5 with SafeStrap 3.72 installed and getting the oddest problem which presents as not enough space to write into the internal SD card (/storage/emulated/0). A bunch of apps start reporting that they have stopped and clearing cache is only a temporary fix. Multiple disk usage tools and commands (Settings->Storage, df, ES File Explorer, DIskUsage) all show gigabytes of free space on the internal memory, and yet, when this problem crops up, I can't do the simplest thing, e.g.,
> cd /storage/emulated/0
> echo x > xyz
(Error: not enough space. I forget the exact message.)
I'm a computer engineer, but not an Android developer, so I've researched and tried a bunch of things such as clearing Dalvik cache, using various commands in DU Speed Booster, etc. but every time it's just temporary.
I've concluded this isn't a space issue, at least not in the internal SD card. I'm guessing it's a space problem elsewhere that manifests itself for some reason as errors trying to write the internal SD card.
I'd be very grateful for some tips on where to look next. Thanks.
elupin said:
I'm running stock NC5 with SafeStrap 3.72 installed and getting the oddest problem which presents as not enough space to write into the internal SD card (/storage/emulated/0). A bunch of apps start reporting that they have stopped and clearing cache is only a temporary fix. Multiple disk usage tools and commands (Settings->Storage, df, ES File Explorer, DIskUsage) all show gigabytes of free space on the internal memory, and yet, when this problem crops up, I can't do the simplest thing, e.g.,
> cd /storage/emulated/0
> echo x > xyz
(Error: not enough space. I forget the exact message.)
I'm a computer engineer, but not an Android developer, so I've researched and tried a bunch of things such as clearing Dalvik cache, using various commands in DU Speed Booster, etc. but every time it's just temporary.
I've concluded this isn't a space issue, at least not in the internal SD card. I'm guessing it's a space problem elsewhere that manifests itself for some reason as errors trying to write the internal SD card.
I'd be very grateful for some tips on where to look next. Thanks.
Click to expand...
Click to collapse
The exact error from above is:
/system/bin/sh: <stdin>[7]: can't create xyz: No space left on device
If I follow with a df command I get:
> df .
Filesystem Size Used Free Blksize
. 9.7G 5.4G 4.3G 4096
df output
You can see that nothing is full, especially not /data/media:
System Tuner (terminal)
========================
=======================
su (su)
=======================
=======================
busybox df -h (su)
=======================
Filesystem Size Used Available Use% Mounted on
tmpfs 908.7M 140.0K 908.5M 0% /dev
none 908.7M 12.0K 908.7M 0% /sys/fs/cgroup
tmpfs 908.7M 0 908.7M 0% /mnt/secure
tmpfs 7.4G 924.3M 6.5G 12% /mnt/secure/asec
/dev/block/vold/179:33
7.4G 924.3M 6.5G 12% /mnt/secure/asec
tmpfs 908.7M 0 908.7M 0% /mnt/asec
/dev/block/dm-0 2.0M 632.0K 1.4M 30% /mnt/asec/com.cjb.listmasterpro-1
/dev/block/dm-1 10.0M 8.4M 1.6M 84% /mnt/asec/com.rerware.android.MyBackupPro-5
/dev/block/dm-2 9.0M 7.2M 1.9M 79% /mnt/asec/com.snoggdoggler.android.applications.doggcatcher.v1_0-19
tmpfs 908.7M 0 908.7M 0% /mnt/obb
/dev/block/platform/msm_sdcc.1/by-name/system
2.7G 2.1G 647.6M 76% /system
/dev/block/platform/msm_sdcc.1/by-name/userdata
9.7G 5.4G 4.3G 55% /data
/dev/block/platform/msm_sdcc.1/by-name/cache
2.0G 39.0M 2.0G 2% /cache
/dev/block/platform/msm_sdcc.1/by-name/efs
13.4M 4.5M 9.0M 33% /efs
/dev/block/platform/msm_sdcc.1/by-name/persdata
8.8M 4.2M 4.7M 47% /persdata/absolute
/dev/block/platform/msm_sdcc.1/by-name/apnhlos
86.0M 11.5M 74.4M 13% /firmware
/dev/block/platform/msm_sdcc.1/by-name/mdm
86.0M 49.8M 36.2M 58% /firmware-mdm
/data/container 9.7G 5.4G 4.3G 55% /mnt/shell/container
/data/media 9.7G 5.4G 4.3G 56% /mnt/shell/emulated
tmpfs 908.7M 0 908.7M 0% /storage/emulated
/dev/block/vold/179:33
7.4G 924.3M 6.5G 12% /mnt/media_rw/extSdCard
/mnt/media_rw/extSdCard
7.4G 924.3M 6.5G 12% /storage/extSdCard
/data/media 9.7G 5.4G 4.3G 56% /storage/emulated/0
/data/media 9.7G 5.4G 4.3G 56% /storage/emulated/0/Android/obb
/data/media 9.7G 5.4G 4.3G 56% /storage/emulated/legacy
/data/media 9.7G 5.4G 4.3G 56% /storage/emulated/legacy/Android/obb
I've cleaned caches, restarted phone, removed secure folder, moved all apps to SD card, ran app booster, and still, system data stays the same, at 25GB. Screenshot from DiskUsage shows the used space - internal memory is mislabeled as storage card. Screenshots from device care show other apps at 55G which can't be true - when I open that I see only small apps there.
output from `df -h`:
Code:
star2lte:/data/enc_user $ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 2.7G 1.6M 2.7G 1% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
tmpfs 2.7G 0 2.7G 0% /apex
/dev/block/dm-0 4.1G 4.0G 119M 98% /
/dev/block/dm-1 622M 616M 5.8M 100% /odm
/dev/block/dm-2 618M 559M 58M 91% /vendor
tmpfs 2.7G 0 2.7G 0% /mnt/sde
/dev/block/sda23 45M 12K 45M 1% /omr
/dev/block/sda21 583M 12M 571M 3% /cache
/dev/block/sda3 16M 2.8M 13M 19% /efs
/dev/block/sdd1 1.8M 556K 1.3M 29% /cpefs
/dev/block/dm-3 53G 47G 4.9G 91% /data
/data/knox/secure_fs/enc_user 53G 47G 4.9G 91% /data/enc_user
/data/knox/secure_fs/enc_media 53G 47G 4.9G 91% /data/knox/secure_fs/enc_media
/data/knox/secure_fs/enc_media 53G 48G 4.9G 91% /mnt/shell/enc_emulated
/data/media 53G 48G 4.9G 91% /storage/emulated
/mnt/media_rw/6112-71F4 60G 49G 11G 83% /storage/6112-71F4
How can I clean up system data?
Android 10, stock, non-root.
Same problem here, 64 GB storage, around 20 GB for user data. How many space I free up less space I have. I don't want do a hard reset and reconfigure all authentication and bank apps.
Device Xiaomi Mi 9, Android 10, no root.