Related
I am running Cyanogen 4.0.4 and would like to know if compcache is enabled. Can someone confirm if my settings are alright?
I have the following details:
Code:
# free
total used free shared buffers
Mem: 97880 95340 2540 0 504
Swap: 24464 17408 7056
Total: 122344 112748 9596
Code:
# df
/dev: 48940K total, 0K used, 48940K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/system: 92160K total, 73844K used, 18316K available (block size 4096)
/system/modules: 640K total, 640K used, 0K available (block size 131072)
/system/xbin: 3328K total, 3328K used, 0K available (block size 131072)
/data: 91904K total, 17680K used, 74224K available (block size 4096)
/cache: 30720K total, 1552K used, 29168K available (block size 4096)
/system/sd: 409986K total, 58588K used, 351398K available (block size 1024)
/data/dalvik-cache: 409986K total, 58588K used, 351398K available (block size 1024)
/sdcard: 15121920K total, 147688K used, 14974232K available (block size 8192)
Code:
# mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
none on /dev/cpuctl type cgroup (rw,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/loop0 on /system/modules type squashfs (ro)
/dev/block/loop1 on /system/xbin type squashfs (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /system/sd type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)
/dev/block/mmcblk0p2 on /data/dalvik-cache type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)
/dev/block//vold/179:1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
if the only thing you have is compache and no linux-swap then compache is working because of the output from the free command
else you should be able to run the following with superuser access through terminal:
sh /system/bin/swap -s
It will show you the pre and post compression data size, as well as the compression rate under compcache.
Or simply use
Code:
# cat /proc/ramzswap
This file only exists when compcache is currently active. You will see its current settings and status:
Code:
DiskSize: 87040 kB
NumReads: 9509
NumWrites: 12188
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
NotifyFree: 1300
ZeroPages: 410
GoodCompress: 78 %
NoCompress: 3 %
PagesStored: 10471
PagesUsed: 3598
OrigDataSize: 41884 kB
ComprDataSize: 13755 kB
MemUsedTotal: 14392 kB
Hi all, i got a SGS branded H3G, but already rooted.
When i try to install Busybox, it says i have no needed room in my /system folder, i do not have installed anything there before.
Then, i ran adb shell, su, df , and got this:
/dev: 166708K total, 0K used, 166708K available (block size 4096)
/mnt/.lfs: Function not implemented
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/system: 282432K total, 281648K used, 784K available (block size 4096)
/data: 1963904K total, 525184K used, 1438720K available (block size 16384)
/dbdata: 130240K total, 24612K used, 105628K available (block size 4096)
/cache: 30784K total, 1552K used, 29232K available (block size 4096)
/efs: 6064K total, 4106K used, 1958K available (block size 1024)
Hey, it's true..only 784k. How can it be? how can i solve?
Anyway, also, some command line at adb wont work, as for " du -sh *", i got this:
$ su
su
# du
du
du: not found
# cd /system
cd /system
# du -sh *
du -sh *
du: not found
# du
du
du: not found
#
wtf
weird, did you do the lag fix?
did you repartition anything?
make sure you have disk space
i see you are rooted, just root it again, just in case
most root update.zip comes with busybox already, are you trying to upgradE?
No lag-fix installed, only clockworkmod recovery.
Yes, i'm rooted with superuser v. 2.3.5 and su binary v. 2131 ef (last one, but no busybox package inside) and i got 3gb disk space available :|
Also, no-repartion was done, it's still branded with original firmware
So... I've been messing around with framework-res.apk. To migrate the file onto the i9000 i rm the original, then cp the new version in. It looks like everytime I do this though, the filesystem never releases free space.
"du -ks /system/*" totals to 260552k, but "df -k /system" shows:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/stl9 282432 281316 1116 100% /system
So it appears like the last 3 or so framework-res.apk's haven't had their space released. I've had to move out some apps from /system/apps to copy in the last couple of framework-res.apk's.
Any suggestions as to how to release the free space?
(My guess is that I remount as rw before copying the file, but there are many processes with handles on the old file so the filesystem cant release the space until reboot, and with the reboot the filesystem is mounted as ro so it can't release the free space?)
** SOLVED **
followed bilboa1's advice on RFS errors in this thread : forum.xda-developers.com/showthread.php?t=797650&highlight=mount+%2Fsystem , fsck_msdos'd the /system partition, did a reboot and regained the free space:
/dev/block/stl9 275.8M 273.7M 2.2M 99% /system
# /system/bin/fsck_msdos -p -f /dev/block/stl9
# reboot
/dev/block/stl9 275.8M 267.2M 8.7M 97% /system
*** solution bump ***
Hi, I have an unlocked, rooted Milestone running 2.1-update1.
I am having some issues getting App2SD up and running.
Everything seems to be working fine except for one piece:
I can't mount the ext2 partition of my SDCard.
I have a 16gb sdcard, formatted with two primary partitions, 14.5gb for FAT32 and 1.5gb for ext2.
busybox was installed ok, all the shell scripts seem to have installed fine as well, however, in order for it to work, the "mount_sd.sh" script has to be able to mount the second partition in order to link /data/app to it - but the damn thing won't mount.
I have tried re-partitioning the SD card multiple times, using multiple different partitioners (gparted in Ubuntu, Minitool in XP, even fdisk in the Android shell itself...) but nothing seems to work - I always get the same error:
Code:
# mount -t ext2 /dev/block//vold/179:2 /system/sd
mount -t ext2 /dev/block//vold/179:2 /system/sd
mount: No such device
The device however, most certainly DOES exist:
Code:
# ls /dev/block//vold
ls /dev/block//vold
179:2
179:1
179:0
I have seen that some people use the /dev/block/mmcblk0 instead of /dev/block//vold/179 - I am unsure as to why (anyone know which one I should be using on the Milestone???) but I tried that as well:
Code:
# mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount: No such device
Again, it tells me the device doesn't exist, when it clearly DOES:
Code:
# ls /dev/block/mmc*
ls /dev/block/mmc*
/dev/block/mmcblk0
/dev/block/mmcblk0p1
/dev/block/mmcblk0p2
When I try to verify the partitions are there in the ADB shell, it looks like /dev/block//vold/179 doesn't exist or is some kind of special device (incidentally, does anyone know wtf the double slashes "//" are for?):
Code:
# fdisk /dev/block//vold/179
fdisk /dev/block//vold/179
fdisk: can't open '/dev/block//vold/179'
However, I CAN fdisk /dev/block/mmcblk0, and it gives me the following partition table:
Code:
# fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
...snip...
Disk /dev/block/mmcblk0: 16.0 GB, 16039018496 bytes
255 heads, 63 sectors/track, 1949 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1762 14153233+ b Win95 FAT32
/dev/block/mmcblk0p2 1763 1949 1502077+ 83 Linux
So, it looks like /dev/mmcblk0 is the correct block device, however, mount tells me this:
Code:
# mount
mount
...snip...
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=101
020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
So, mount is telling me that the first partition is mounted onto /sdcard from /dev/block//vold/179:1
I am confused. The only thing left I need to do in order to get App2SD working on my Milestone, is to mount the bloody second partition of my SD card and link it to the file system, yet the damn thing refuses to mount.
Does anyone know where I am going wrong here?
Which is the correct block device I should even be trying to mount /dev/block/mmcblk0 or /dev/block//vold/179:2?
I don't want to flash to an unofficial 2.2 and I have everything else working just the way I want it, so I'd rather not reset either.
There MUST be a solution somewhere, but I am getting frustrated.
Thanks for any help you can give me!
Hello!
I'm having exactly the same problem... I've been trying to find a solution for this problem for the last 3 hours, but I can't figure out a way...
Can anyody give us a light??
Thanks!
Same question here. Partitioned more than a month ago, but then I reached a dead end. I don't know a reliable way to mount the ext2 partition. I'm familiar with Linux, and I have tried all kinds of crazy shell scripts, but the Android filesystem is still a bit alien to me.
By the way, what is this App2SD that you speak of? It's something different from the Apps2SD app on Froyo, right?
JoeDuncan said:
Code:
# mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount: No such device
Click to expand...
Click to collapse
A shot in the dark would be ext2.ko is not insmodded ... ?
got this problem to on stock US froyo kernel for Samsung Galaxy 5. I also suspected ext2 was missing but it seems compiled into kernel.
Code:
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev inotifyfs
nodev devpts
ext2
nodev ramfs
vfat
nodev nfs
rfs
For the MS, you have to insert a ext2 Kernel module, look around here on the forums..
Depending on which module-version you're using try "-t auto" instead of "-t ext2"
Also you should use "/dev/block/mmcblk0p2" if this is your ext2 partition
Besides, there should be some packages available which contain the necessary scripts and files to install this automatically and at boot, applicable as OR-updates
It was my understanding that Apps2SD could not be used on 2.1, you needed 2.2 to use that app. Although I have the same issue with Links2SD which is suppose to work with 2.1. I can't get anything to see an ext2 or 3 or Fat partition.
My amator tries
Hy,
I've got the same problem on Cyanogen and Goapk roms:
mount -t auto /dev/block/mmcblk0p2 /sd-ext
doesn't work
I verified sd-ext was present
mkdir /sd-ext
Nothing changed.
My mount description is somethime using vold instead of mmcblk0p... I don't really understand.
However I succeeded to mount sdext by using busybox (on goapk rom)
busybox mount -r -w -t auto /dev/block/mmcblk0p2 /sd-ext
result mount:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g
id=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1
000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso
8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0
/dev/block/mmcblk0p2 /sd-ext ext2 rw,errors=continue 0 0
Just in case, If somebody can help me:
*I have a symlink /data/drm =>/data/local :how to unsymlink it? (unbind isn't present and replacement doesn't work:" Invalid cross-device link")
*perl script are unable to decompresse boot.img, how to change init.rc in this case?
thanks
symlinks
lamidesbetes said:
*I have a symlink /data/drm =>/data/local :how to unsymlink it? (unbind isn't present and replacement doesn't work:" Invalid cross-device link")
Click to expand...
Click to collapse
Symlinks can be removed with the rm command.
The "cross device link" error happens when one uses the ln command without the "-s" option (so attempting a hard link instead of symlink).
I installed the hypersense nova rom on August. It's telling me no enough space.
However, there's plenty of space in /sd-ext:
Code:
sh-3.2# df /system /sd-ext /data /sdcard
/system: 225280K total, 209508K used, 15772K available (block size 4096)
/sd-ext: 1032056K total, 308808K used, 723248K available (block size 4096)
/data: 211200K total, 188952K used, 22248K available (block size 4096)
/sdcard: 2820736K total, 1362320K used, 1458416K available (block size 16384)
There's no a2sd command, since they say it's already embedded. I have tried to move apps from Settings>Applications>Manage Applications> SD Card... Move to SD Card. But it seems they are moved to /sdcard, not /sd-ext (e.g. Jorte)
Code:
sh-3.2# df /system /sd-ext /data /sdcard
/system: 225280K total, 209508K used, 15772K available (block size 4096)
/sd-ext: 1032056K total, 308804K used, 723252K available (block size 4096)
/data: 211200K total, 188952K used, 22248K available (block size 4096)
/sdcard: 2820736K total, 1367552K used, 1453184K available (block size 16384)
Code:
sh-3.2# mount
...
/dev/block/dm-0 /mnt/asec/jp.co.johospace.jorte-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,short
name=mixed,utf8,errors=remount-ro 0 0
Is it possible to move apps from /data to /sd-ext manually? Does it makes sense?
bitozoid said:
I installed the hypersense nova rom on August. It's telling me no enough space.
However, there's plenty of space in /sd-ext:
Code:
sh-3.2# df /system /sd-ext /data /sdcard
/system: 225280K total, 209508K used, 15772K available (block size 4096)
/sd-ext: 1032056K total, 308808K used, 723248K available (block size 4096)
/data: 211200K total, 188952K used, 22248K available (block size 4096)
/sdcard: 2820736K total, 1362320K used, 1458416K available (block size 16384)
There's no a2sd command, since they say it's already embedded. I have tried to move apps from Settings>Applications>Manage Applications> SD Card... Move to SD Card. But it seems they are moved to /sdcard, not /sd-ext (e.g. Jorte)
Code:
sh-3.2# df /system /sd-ext /data /sdcard
/system: 225280K total, 209508K used, 15772K available (block size 4096)
/sd-ext: 1032056K total, 308804K used, 723252K available (block size 4096)
/data: 211200K total, 188952K used, 22248K available (block size 4096)
/sdcard: 2820736K total, 1367552K used, 1453184K available (block size 16384)
Code:
sh-3.2# mount
...
/dev/block/dm-0 /mnt/asec/jp.co.johospace.jorte-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,short
name=mixed,utf8,errors=remount-ro 0 0
Is it possible to move apps from /data to /sd-ext manually? Does it makes sense?
Click to expand...
Click to collapse
Easy, just install an a2sd script
Sent from my Nexus One using Tapatalk 2
humzaahmed155 said:
Easy, just install an a2sd script
Click to expand...
Click to collapse
Thanks. I found I was not the only one with this issue. Some people have upgraded the a2sd script, despite they say it is not necessary:
http://forum.xda-developers.com/showthread.php?p=31802698&highlight=a2sd#post31802698
Anyway, I have just upgraded to last version (november 16th). I hope that fixes the issue. Anyway, I've found that data storage for some apps gets bigger as time goes on (e.g. google reader). Deleting the user data from some apps at Settings>Applications>Manage Applications may free a lot of space.