Database Info

[CM6.3] Link2SD Ext 4 problems?

Link2SD is not working
I converted an ext2 partition with the OpenRecovery XT720 sd card tools to ext 4, but I guess something went wrong. I also created the link2sd folder in /sd-ext, but link2sd is not working. Here is my sdcard-info.txt:
FIX ME! implement ttyname() bionic/libc/bionic/stubs.c:360
Mon Sep 19 23:31:19 GMT 2011
OpenRecovery-XT720-01
Mounted filesystems
-------------------
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/mtdblock7 /system yaffs2 rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/mmcblk0p2 /sddata ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock10 /cust yaffs2 rw,nodev,noatime,nodiratime 0 0
Directory configuration
-----------------------
drwxrwx--x 1 system system 2048 Sep 19 20:15 /cache/dalvik-cache
ls: /cache/dc: No such file or directory
drwxrwx--x 1 system system 2048 Sep 19 13:30 /data/app
drwxrwx--x 1 system system 2048 Sep 19 00:32 /data/app-private
drwxrwx--x 1 system system 2048 Sep 19 13:30 /data/dalvik-cache
drwxrwx--x 1 system system 2048 Sep 19 00:32 /data/sdext2
ls: /sddata/app: No such file or directory
ls: /sddata/app-private: No such file or directory
ls: /sddata/dalvik-cache: No such file or directory
drwxrwx--x 2 system system 1024 Sep 20 04:59 /sddata/link2sd
Directory /cache/dalvik-cache contains 110 files
Directory /data/app contains 25 files
Directory /data/app-private contains 0 files
Directory /data/dalvik-cache contains 38 files
Directory /data/sdext2 contains 0 files
Directory /sddata/link2sd contains 0 files
SD card partition table:
------------------------
Disk /dev/block/mmcblk0: 16.0 GB, 16050552832 bytes
4 heads, 16 sectors/track, 489824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 33 473760 15159296 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 473793 489792 512000 83 Linux
Partition 2 does not end on cylinder boundary
EXT partition properties:
-------------------------
tune2fs 1.41.10 (10-Feb-2009)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 66bd2797-2734-06cd-13d5-5b21e456ff4f
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal dir_index filetype needs_recovery extent sparse_super uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 64512
Block count: 512000
Reserved block count: 25189
Free blocks: 495587
Free inodes: 64500
First block: 1
Block size: 1024
Fragment size: 1024
Blocks per group: 8192
Fragments per group: 8192
Inodes per group: 1024
Inode blocks per group: 128
Filesystem created: Sun Sep 18 23:46:39 2011
Last mount time: Tue Sep 20 05:11:44 2011
Last write time: Tue Sep 20 05:11:44 2011
Mount count: 5
Maximum mount count: 20
Last checked: Tue Sep 20 02:10:26 2011
Check interval: 15552000 (6 months)
Next check after: Sun Mar 18 02:10:26 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: d4776a55-3311-7ed1-2c5f-13686f8dbb1a
Journal backup: inode blocks
Please help me. Thank you.

Hmmm. I don't see anything that looks obviously wrong here. I'll take a look at the boot scripts. Did it work previously using ext2 on the same ROM? Can you describe any error messages?

Maybe I missed some information!? The folder /sd-ext/link2sd is still emty. After activating link2sd in Dexter's Froyo by creating the folder app and a reboot link2sd worked. Is this different in CM 6.3?
Sent from my Milestone XT720 using XDA App

Winsten said:
Maybe I missed some information!? The folder /sd-ext/link2sd is still emty. After activating link2sd in Dexter's Froyo by creating the folder app and a reboot link2sd worked. Is this different in CM 6.3?
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
No, it should be the same. What error is Link2SD displaying?

Okay, now a noob question: Is the link2sd function integrated in CM 6.3 or do I have to download the link2sd app from the market? And where will I find the error message from link2sd?
Sent from my Milestone XT720 using XDA App

Winsten said:
Okay, now a noob question: Is the link2sd function integrated in CM 6.3 or do I have to download the link2sd app from the market? And where will I find the error message from link2sd?
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
Yes, you have to install the app from the market. The app will display the error message. All the ROM does is handle mounting /sd-ext/link2sd to /data/sdext2 (which the Link2SD app uses).
http://forum.xda-developers.com/showthread.php?t=919326
https://market.android.com/details?id=com.buak.Link2SD&hl=en

This was the missing information I was talking about Great, link2sd works now. Thanks for your help.
Sent from my Milestone XT720 using XDA App

[Q] samsung galaxy wifi 5.0 boot.img

Does this device have a boot.img file that is accessible and editable?
I have the following details from the system files:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 6 256 mmcblk0p6
179 7 1280 mmcblk0p7
259 0 1280 mmcblk0p8
259 1 5120 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 7680 mmcblk0p11
259 4 7680 mmcblk0p12
259 5 296960 mmcblk0p13
259 6 137216 mmcblk0p14
259 7 65536 mmcblk0p15
259 8 1970176 mmcblk0p16
259 9 5252096 mmcblk0p17
179 8 1931264 mmcblk1
179 9 1930240 mmcblk1p1
# grep "mmcblk0" init.rc
mount rfs /dev/block/mmcblk0p13 /system check=no
mount rfs /dev/block/mmcblk0p13 /system check=no
mount rfs /dev/block/mmcblk0p13 /system ro remount
mount rfs /dev/block/mmcblk0p10 /efs nosuid nodev check=no
# mount rfs /dev/block/mmcblk0p16 /data nosuid nodev check=no
mount rfs /dev/block/mmcblk0p16 /data nosuid nodev crypt check=no
mount rfs /dev/block/mmcblk0p14 /dbdata nosuid nodev crypt check=no
#mount rfs /dev/block/mmcblk0p14 /dbdata nosuid nodev check=no
mount rfs /dev/block/mmcblk0p15 /cache nosuid nodev check=no
mount j4fs /dev/block/mmcblk0p9 /mnt/.lfs
# cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p13 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p10 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p14 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p15 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p9 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

no mtd in /proc
I also found that there is no /proc/mtd which makes it hard to figure out which mount points are the boot and recovery images.
Code:
# ls /proc/
param
rfs
last_kmsg
batt_info_proc
uid_stat
pvr
apm
sysrq-trigger
partitions
diskstats
crypto
kpageflags
kpagecount
kmsg
softirqs
version
uptime
stat
meminfo
loadavg
interrupts
devices
cpuinfo
cmdline
locks
filesystems
vmallocinfo
zoneinfo
vmstat
pagetypeinfo
buddyinfo
kallsyms
modules
timer_list
iomem
ioports
execdomains
sched_debug
cpu
asound
scsi
misc
fb
wakelocks
irq
cgroups
sys
bus
tty
driver
fs
sysvipc
net
mounts
self
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
37
38
39
40
41
42
49
51
52
53
54
55
56
57
58
59
60
61
62
64
67
68
69
71
72
73
74
75
76
77
78
79
80
84
86
87
91
93
100
120
199
207
212
213
217
234
276
309
419
557
566
574
695
995
1391
1409
2159
5135
5769
8293
8301
9704
10957
10959
10973
14462
14493
21343
32673

YP-G70 - 3 boot logos... wtf?
I successfully flashed the boot logo and replaced the animated boot logo but there is still a samsung boot logo showing up on this device.
When I boot I see my custom boot logo which is written to param.lfs after modifying the name of the original logo.jpg to l0g0.jpg and reflashing via odin. Heimdell won't successfully flash this device although it can extract the pit file without problems.
The custom logo in /mnt/.lfs displays for about 2 seconds then I see the original "samsung" logo for about 5 seconds then I see the custom boot animation.
I replaced the boot animation like this:
# cd /system/bin
# mv samsungani samsungloopani
# mv bootanimation samsungani
# reboot
I added my own custom boot animation "sanim.zip" to /system/media which plays just fine. Samsung have renamed bootanimation.zip to sanim.zip for no apparent reason.
I can't find any info anywhere about this mysterious third logo that shows up between the boot logo and the boot animation.
I found a logo file in /sbin/ called fota.png but it seems that it is not possible or at least undocumented on how to retrieve and edit the samsung "boot.img" to replace /sbin/fota.png with my own logo. Even if I did that I am not certain that it would solve the problem.

no one has any hints?

Turns out the "zImage" partition is located on /dev/block/mmcblk0p12
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/zImage
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/factoryfs.rfs
dd if=/dev/block/mmcblk0p9 of=/mnt/sdcard/param.lfs

hi i like ur thread
so can i change the
GT-S7500 Logo before boot animation

[Q] CronosX - random reboot / strange slowness

Hi!
I'm using this mod for some time, and i'm pretty much happy with it..
one of the "little" things which keeps me annoyed is that it just randomly reboots.. i'm going through the logs but i can't really figure out what happens because of my lack of programming skills
is there any tips what normally causes these? or what should i look for in the logs?
#2 i like games, so i want to play on my phone.. thing is, that most games just takes me back to home screen after loading for some time.. even those which i know work on the phone!
best example is "where is my water". i played it a lot, now it's hardly starting, and when it does, it is sooooooooooooooooooooooooooooooooooooooooooooooooooo slow. like i want to play Crysis on a commodore64 ..
currently the CPU is set on 1 ghz, i played with heapsizes, and now it is on 24
plus my avg free ram is ~25.. although i'm not using widgets or anything :\
suggestions?

Reboots could be cause by over ckocking.
1gz should be oka but what is vessel set at?
heap size should be 32.
i recomend the ram manager.
Sent from my SGH-T759 using xda premium

mchlbenner said:
Reboots could be cause by over ckocking.
1gz should be oka but what is vessel set at?
heap size should be 32.
i recomend the ram manager.
Sent from my SGH-T759 using xda premium
Click to expand...
Click to collapse
i've edited the overclock in etc/initd
current settings are:
1000 mhz 72 vsel
800 - 62
720 - 50
500 - 42
250 - 30
i found lots of ppl saying 72 is good for 1ghz
i changed the heap size to 32 and i'll take a look for that ram manager soon

mchlbenner said:
Reboots could be cause by over ckocking.
1gz should be oka but what is vessel set at?
heap size should be 32.
i recomend the ram manager.
Click to expand...
Click to collapse
Also reboots could cause by sdcard.
Check it in openrecovery.

My xt720 is overclocked at 1GHz 66volt . On cm6.3.7 . Works incredibly well ! My average ram is about 110mb (no joke) with some "trick" . ~25mb ram is really too problematic to play where is my water . I almost able to play heavy games (temple run , eternity warrior , contract killer etc) , with the help of chainfire 3d . Install chainfire 3d driver if you haven't , totally awesome .

fjfalcon said:
Also reboots could cause by sdcard.
Check it in openrecovery.
Click to expand...
Click to collapse
i checked it in OR, here is the result:
FIX ME! implement ttyname() bionic/libc/bionic/stubs.c:360
Tue Apr 17 15:13:20 GMT 2012
OpenRecovery-XT720-01
Mounted filesystems
-------------------
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/mtdblock7 /system yaffs2 rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nodev,noatime,nodiratime 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock10 /cust yaffs2 rw,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p2 /sddata ext4 rw,barrier=1,data=ordered 0 0
Directory configuration
-----------------------
drwxrwx--x 1 system system 2048 Mar 28 07:37 /cache/dalvik-cache
ls: /cache/dc: No such file or directory
drwxrwx--x 1 system system 2048 Mar 28 07:33 /data/app
drwxrwx--x 1 system system 2048 Mar 28 06:56 /data/app-private
drwxrwx--x 1 system system 2048 Apr 14 17:15 /data/dalvik-cache
drwxrwxr-x 1 root root 2048 Mar 28 07:06 /data/sdext2
drwxrwx--x 2 system system 2048 Apr 14 17:15 /sddata/app
drwxrwx--x 2 system system 1024 Mar 28 07:33 /sddata/app-private
ls: /sddata/dalvik-cache: No such file or directory
ls: /sddata/link2sd: No such file or directory
Directory /cache/dalvik-cache contains 1 files
Directory /data/app contains 0 files
Directory /data/app-private contains 0 files
Directory /data/dalvik-cache contains 121 files
Directory /data/sdext2 contains 0 files
Directory /sddata/app contains 26 files
Directory /sddata/app-private contains 0 files
SD card partition table:
------------------------
Disk /dev/block/mmcblk0: 8018 MB, 8018460672 bytes
255 heads, 63 sectors/track, 974 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 855 6867756 b Win95 FAT32
/dev/block/mmcblk0p2 856 973 947835 83 Linux
EXT partition properties:
-------------------------
tune2fs 1.41.10 (10-Feb-2009)
Filesystem volume name: EXT2
Last mounted on: <not available>
Filesystem UUID: 06be1b5c-690c-cd01-003a-1b5c690ccd01
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 237568
Block count: 947835
Reserved block count: 47391
Free blocks: 825787
Free inodes: 237528
First block: 1
Block size: 1024
Fragment size: 1024
Blocks per group: 8192
Fragments per group: 8192
Inodes per group: 2048
Inode blocks per group: 256
Last mount time: Tue Apr 17 22:13:04 2012
Last write time: Tue Apr 17 22:13:04 2012
Mount count: 1
Maximum mount count: 20
Last checked: Tue Apr 17 22:12:59 2012
Check interval: 15552000 (6 months)
Next check after: Sun Oct 14 22:12:59 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Journal backup: inode blocks
Click to expand...
Click to collapse
says anything useful?

fjfalcon said:
Also reboots could cause by sdcard.
Check it in openrecovery.
Click to expand...
Click to collapse
As fifalcon wrote the memory card can cause reboot.
The sdcard the phone came with crapy you want to replace it.
Sent from my SGH-T759 using xda premium

mchlbenner said:
As fifalcon wrote the memory card can cause reboot.
The sdcard the phone came with crapy you want to replace it.
Sent from my SGH-T759 using xda premium
Click to expand...
Click to collapse
i have an 8gb transcend class 10, which should be in perfect condition, or does the log say otherwise?

the last random-reboot i noticed was currently after taking a photo, which has not been stored on the card.. that makes me think it's all about the SD card :\
how can i check if it is the problem or the connectivity between the card and phone?

the cause is the system..
i'm not saying that xt720's programmers here is not good enough but apparently building a perfect rom is a hard task..
maybe the specific cause of those reboots is something with the memory access.. i'm not sure is it only with external memory or internal too or maybe also with the ram access..
my other example is my phone always reboot after an alarm event.. not only after using an app or playing games..
hmm i should try to remove my sdcard and use my phone without it i wonder is there still will be any strange reboot..???

The frist thing the devs have done a great job thing could be diffrent if not for the locked bootloader.
The milestone is only 256 ram.
Sent from my SGH-T759 using xda premium

i bought a new SD card.. rom works like magic! thank you all!
strange it feels like with my prev card it hasn't even worked like this before.. maybe that was a fake? dunno.. now it's good

[Q] Error mounting /mnt/sdcard

Hi,
i have a big problem with mit GT-I5800...
I have only 171Mb free because the internal SD Card is not mountable....
My actual Rom is KISADWORX 2.6.1
If i am in the recovery and try to format or mount my internal sdcard i got the following error:
E:Can´t mount /dev/block/mmcblk0p1 (or NULL)
(No such file or directory)
Error mounting /mnt/sdcard
Skipping format....
done
What i have tried:
Minitool Partiotion Wizard (i see only my PC Drives but no Galaxy SD Card or something like that)
Flash Stock Rom
Flash Kisadworx 2.6.1
Flash Kyrillos Rom 9.7
Tried this in adb shell: mkfs.ext2 /dev/block/stl7
(error message because allready mounted)
mount gives that;
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
nodev on /tmp type tmpfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl6 on /system type rfs (rw,nodev,noatime,nodiratime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
/dev/block/stl7 on /data type rfs (rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437
/dev/block/stl4 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437)
I can see the Device (only if USB debugging is on) in Windows Explorer as Drive G: But i can not format it, because there is no drive inside
cat /proc/partitions
major minor #blocks name
139 0 513024 tfsr0
139 1 256 tfsr1
139 2 1280 tfsr2
139 3 512 tfsr3
139 4 8192 tfsr4
139 5 7680 tfsr5
139 6 225280 tfsr6
139 7 207360 tfsr7
139 8 38912 tfsr8
139 9 7168 tfsr9
139 10 16384 tfsr1
137 0 513024 bml0/
137 1 256 bml1
137 2 1280 bml2
137 3 512 bml3
137 4 8192 bml4
137 5 7680 bml5
137 6 225280 bml6
137 7 207360 bml7
137 8 38912 bml8
137 9 7168 bml9
137 10 16384 bml10
138 4 4352 stl4
138 6 217600 stl6
138 7 200192 stl7
138 8 34816 stl8

Can someone post the result of:
mount
and cat /proc/partions
???
Should i have an internal sd-card if no extrnal is inserted ?

This phone had problems with some sd cards. I had to change it because I had lot of files corrupted.
Enviado desde mi GT-I8190N mediante Tapatalk

CORRECT
Ya its your SD Problem ....... Changing SD is Cool .....
Can yousay the SD card is Compatable With 32 GB ....\
Anybody Can Say ????

My phone shows storage size 16 GB, but partition USERDATA is 27 GB - what to believe?

I have Soyes XS phone. I bought a version with 2GB RAM and 16 GB internal storage. And when I look at Settings > Storage it shows Total space 16.00 GB. So far everything is logical.
But then I used SP Flash Tool and used Read Back to download partition PGPT to my PC. That partition contains the partition table for the internal storage. Program sgdisk shows that partition USERDATA alone is bigger that 16 GB:
Code:
Number Start (sector) End (sector) Size Code Name
22 6422528 61037567 26.0 GiB 0700 userdata
Then I downloaded partition USERDATA to my Linux PC. According to program tune2fs, the partition size is 6826880 blocks * 4096 bytes/block = 27962900480 bytes! I checked the file system with fsck, and it found no errors.
Code:
[[email protected] Soyes-XS]$ ls -l
-rw-r--r--. 1 root root 27962900480 Jul 17 02:43 USERDATA
[[email protected] Soyes-XS]$ file *
USERDATA: Linux rev 1.0 ext4 filesystem data, UUID=c25d03d9-ea27-3358-873e-b911bfaab62b, volume name "data" (extents) (large files)
[[email protected] ~]# mount -r -o loop /d0/tmp/Soyes-XS/USERDATA /mnt/
[[email protected] ~]# fsck -n /dev/loop0
fsck from util-linux 2.33.2
e2fsck 1.44.6 (5-Mar-2019)
Warning! /dev/loop0 is mounted.
data: clean, 1980/1712128 files, 253823/6826880 blocks
[[email protected] ~]# tune2fs -l /dev/loop0
tune2fs 1.44.6 (5-Mar-2019)
Filesystem volume name: data
Last mounted on: /data
Filesystem UUID: c25d03d9-ea27-3358-873e-b911bfaab62b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 1712128
Block count: 6826880
Reserved block count: 4096
Free blocks: 6573057
Free inodes: 1710148
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 126
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Last mount time: Tue Jul 16 12:07:14 2019
Last write time: Tue Jul 16 12:07:14 2019
Mount count: 27
Maximum mount count: -1
Last checked: Thu Jan 1 02:00:00 1970
Check interval: 0 (<none>)
Lifetime writes: 79 GB
Reserved blocks uid: 10010 (user unknown)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
What is the real size of my internal storage? If the size is only 16 GB, is there a danger that the phone will eventually try to write beyond the 16 GB and fail?

I though u r lucky

It's possible that your original partition has hard links and they were copied over as separate files by the backup tool. You can use the du program to check the size of the original partition properly without counting hard links more than once.