• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help df -h wtf

Andronix

Android Enthusiast
could anyone tell me which device sits behind mtdblock* partitions? don't tell me it's ram.


# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 46.9M 0 46.9M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock1 87.5M 87.5M 0 100% /system
/dev/block/mtdblock2 1.3M 1.1M 120.0k 91% /userdata
/dev/block/mmcblk0p1 944.9M 130.4M 804.9M 14% /data
/dev/block/mtdblock5 35.8M 1.6M 34.2M 4% /dbdata
/dev/block/mtdblock4 87.5M 4.9M 82.6M 6% /cache
/dev/block/vold/180:2
6.6G 2.7G 3.8G 41% /sdcard
/dev/block/vold/179:9
7.6G 1.5G 6.1G 19% /sdcard/sd
#
 
i dont know, but that looks like ram to me

the phone only has 128mb ram aswell lol

wow so what about previous posts claiming that there should be around 196mb or ram?
say its only 128mb ram are we going to be affected by that? say not being able to play 3d games or even say compass is slow coz of lack of ram?
 
someone did some checks early when i made this statement last week as people believed it to be 192 but they found it was 128

dont know why samsung have done that or what implication it has as most devices for android now house 288

people made assumptions on what the hardware was as most if it is similar to the g1/dream

gsm arena and many other sites also show this as being 128mb ram
 
Hmm no it is 192mb. There's 128mb ram external to the MSM die, and 64mb internal to it. I don't know how whoever it was checked, but maybe they only saw the 128mb bit.

Its _definatly_ 192mb, i've checked myself.
 
what is caching used for if not keeping libs in RAM? preload all of them when you're already low on resources doesnt sound like good idea.

i've seen many distros, back when 64mb ram was very much and never seen anything like that.
 
According to /proc/self/mountinfo

1 1 0:1 / / ro - rootfs rootfs ro
11 1 0:11 / /dev rw - tmpfs tmpfs rw,mode=755
12 11 0:10 / /dev/pts rw - devpts devpts rw,mode=600
13 1 0:3 / /proc rw - proc proc rw
14 1 0:0 / /sys rw - sysfs sysfs rw
15 1 0:12 / /sqlite_stmt_journals rw - tmpfs tmpfs rw,size=4096k
16 1 31:1 / /system ro - yaffs2 /dev/block/mtdblock1 ro
17 1 31:2 / /userdata rw,nosuid,nodev - yaffs2 /dev/block/mtdblock2 rw
18 1 180:1 / /data rw,nosuid,nodev - ext3 /dev/block/mmcblk0p1 rw,errors=remount-ro,debug,commit=2,data=journal
19 1 31:5 / /dbdata rw,nosuid,nodev - yaffs2 /dev/block/mtdblock5 rw
20 1 31:4 / /cache rw,nosuid,nodev - yaffs2 /dev/block/mtdblock4 rw
21 1 180:2 / /sdcard rw,nosuid,nodev,noexec - vfat /dev/block/vold/180:2 rw,dirsync,uid=1000,gid=1000,fmask=0711,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8
22 21 179:9 / /sdcard/sd rw,nosuid,nodev,noexec - vfat /dev/block/vold/179:9 rw,dirsync,uid=1000,gid=1000,fmask=0711,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8

This seems to suggest that mtdblock1, 2, 4 and 5 are part of the flash that the system uses to store the os on (As suggested by the naming convention). This is separate from the 8gb built-in memory. So there is no ram mount here.
 
Back
Top Bottom