Database Develop

Is there a way to make apps use /sdcard/ApplicationData rather than /sdcard ?

Is there a way to make all applications store their data in a folder other than /sdcard (root folder on the sd card) ?
I'm planning on rooting and thought that this time round I can keep my sdcard nice and organized by creating an "ApplicationData" folder in the root of the sdcard and somehow configuring android to use that.
On a similar note, can I move the DCIM (camera photos) to a different location too?
Will the below change-mount-point idea work?
Maybe as root we can
1) un-define /sdcard (in /etc/fstab) //or wherever its defined
2) define /sdcard as /dev/<hdb0>/ApplicationData //change hdb0 to the appropriate device/partition
thanks.

Yeah, I see your point... but quite frankly, I believe it's upto the app developers [my knowledge of the Android world is still from the stone-age!!]... if the app specifies that it's data will be stored in /sdcard/AppName, there's not much you can do, unless you can modify the app...

I was thinking that maybe as root we can
1) un-define /sdcard (in /etc/fstab) //or wherever its defined
2) define /sdcard as /dev/<hdb0>/ApplicationData
edit: added to post#1

britoso said:
I was thinking that maybe as root we can
1) un-define /sdcard (in /etc/fstab) //or wherever its defined
2) define /sdcard as /dev/<hdb0>/ApplicationData
edit: added to post#1
Click to expand...
Click to collapse
I did think of this too...
/sdcard --> /sd/AppData
rest of sd card --> /sd
but I think it would mean some other changes as well... for example... the mount usb functionality would have to be modified to mount/unmount a different volume...

So heres the contents of my fstab file:
Code:
C:\>adb shell cat /system/etc/fstab
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /system/sd auto rw
/system/modules/modules.sqf /system/modules squashfs ro,loop
/system/xbin/xbin.sqf /system/xbin squashfs ro,loop
I'll try changing line 4 (/sdcard), I'm guessing /system/sd is for when I apps2sd is enabled.
Question: How do I escape from INSERT/EDIT mode in VI? Tried pressing trackball+1, trackball+1+2...didnt work

Hey britoso!
Keep us updated with your accomplishments. I, personally, am very interested in being able to achieve this.
Good luck!

update: that didnt work.
Note: the way to get the ESCAPE character is CONTROL + [ (hold the trackball then press [ ). The control key is configurable and defaults to the Jogball/TrackBall
here are the contents of my fstab file, the camera app is still writing to the root of the sdcard (/sdcard/DCIM)
Code:
C:\>adb shell cat /system/etc/fstab
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mmcblk0p1 /sdcard/AppData vfat rw
/dev/block/mmcblk0p2 /system/sd auto rw
/system/modules/modules.sqf /system/modules squashfs ro,loop
/system/xbin/xbin.sqf /system/xbin squashfs ro,loop
Heres the output of "df"
Code:
C:\>adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 197600 0 197600 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 148480 100088 48392 67% /system
/dev/block/mtdblock5 200960 63752 137208 32% /data
/dev/block/mtdblock4 97280 39628 57652 41% /cache
/dev/block//vold/179:1
15643712 6843256 8800456 44% /sdcard

@britoso
This is what I found out about mounts in Android...
The init program directly mounts all filesystems and devices using either hard-coded file names or device names generated by probing the sysfs filesystem (thereby eliminating the need for a /etc/fstab file in Android).
And from what I see in your df output, it didn't mount /sdcard/AppData...
Have a few ideas in mind... gonna try 'em out now...

craigacgomez said:
gonna try 'em out now...
Click to expand...
Click to collapse
thanks for the info. Let us know how it works out.

Here's what I reached finally...
To achieve this, I have 2 ideas...
1. We gotta modify the init and change the SD mount point to AppData and add another for the rest of the SD... this however would require a rebuilt ROM (I can't edit init on the phone, need to edit init.c from the source)
2. We push some startup scripts to achieve this, but so far, I haven't been able to mount anything else on /sdcard (operation failed), but I think I'm doing something wrong...
Didn't get much time to experiment... and it mite be a busy end of week for me... but I'll try to squeeze in so time to get this...

Why not ask Cyanogen to do this for us in his next ROM?
Or your next favorite modder?
I'm sure they'll like this idea!?

theres a setting in /init.rc that may help
Code:
export EXTERNAL_STORAGE /sdcard
However / is mounted read-only
mount
rootfs on / type rootfs (ro,relatime)
Click to expand...
Click to collapse

Need Some More Help Partitioned and loaded rom but internal mem is still under 32 sho

i used amon ra v1,5,2 because it is stable but i checked my internal mem and it says 32mb which is still regular phone mem
do i need ap2sd to get my 96mb or do i need to convert ex3 to ex4 or is there something im missing

What spl are you using?
Also, type
Code:
busybox df -h
in terminal and let us know the output.

I don't know how to tell which spl
But this is the output
My busy box kmoo sd Details $ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3 AO
So what do I do next

DroidFreek said:
I don't know how to tell which spl
But this is the output
My busy box kmoo sd Details $ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3 AO
So what do I do next
Click to expand...
Click to collapse
Doesn't look right . Your df -h output should look something like this
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 47.9M 12.0K 47.8M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_st
/dev/block/mtdblock3 90.0M 66.4M 23.6M 74% /system
/dev/block/loop0 512.0K 512.0K 0 100% /system/modules
/dev/block/loop1 2.8M 2.8M 0 100% /system/xb
/dev/block/mtdblock5 89.8M 27.4M 62.4M 30% /data
/dev/block/mtdblock4 30.0M 24.1M 5.9M 80% /cache
/dev/block/mmcblk0p2 457.3M 33.0M 400.0M 8% /system/sd
/dev/block/mmcblk0p2 457.3M 33.0M 400.0M 8% /data/dalv
/dev/block//vold/179:1
6.9G 6.3G 670.3M 91% /sdcard
where /system/sd is your apps2sd partition (if you have it) and /data is your internal storage.
I have 62megs free in my data, I'm not sure where you hear 96 megs but its complete unnecessary to have that much space free. I've yet to experience any slowdowns or low mem warnings. Also remember.... some devs put parts of their rom on /data partition and that will decrease your available space.
Also, there's absolutely NO WAY you should be getting low mem warning with 34 megs free. That only happens when you have less then 10 megs available. Apps2sd is the obvious choice if you want to have as much phone mem available as possible.

Your a real geniuos ty I got it to work but what is the secondary sd for what does it store and how can I access it I am currently using estrongs explorer

Don't know about estrongs... never used it. Rule of thumb, if it asks for SU access the first time you run it - then it will be able to access it.
I'll break it down for ya
Internal memory:
/system - your rom
/system/app - system files (google apps, dialer, contacts etc)
/system/**** - extra stuff that our devs include (thanks to them)
/data/app - non-protected apps
/data/app-private - protected apps
/data/dalvik-cache - working files for all apps
/data/data - your settings
/system/sd - aka your secondary partition, aka apps2sd is a part of your sdcard. Only accessible in Linux or in terminal. When you have apps2sd set up, your phone will bypass /data/app, data/app-private and /data/dalvik-cache and forward those files to /system/sd/app, /system/sd/app-private and /system/sd/dalvik-cache. It will still use /data/data for all of your settings. I know it's a lot of slashes there but it will start making sense as you progress with Android hacking.
If you want to see what's on secondary sd just type this in terminal
Code:
ls /system/sd
This will give you a print-out of the apps that are on your sd.
Anything else I'm forgeting?

Ok this is the new output
$ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3**** 67.5M**** 61.8M***** 5.7M* 92% /system/dev/block/loop0

Is it possible you can give me a list of all the commands for terminal

http://www.droidforums.net/forum/droid-hacks/26036-linux-commands-android.html
Try this, some basics.

want to make exact image of my whole os and all apps in it
Is it possible to make an exact image of of my whole os including the apps web bookmarks and etc

sort of like the program iamgeburn does for pc

yea a nandroid back up. check your recovery for a back up option

So i just head to recovery and choose nanodroid then choose backup right
after soing so where does it save to and how can i retrieve it after a complete wipe of sd and system

saved on your sdcard under nandroid.
To use it, in recovery select restore and choose the nadroid that you want to recover. Your now back to exactly where you were when you created it.
easy peasy.

A2SD Error?

Been searching tons of forums for answer, seems like no ones problem is quite like mine though, so...Time to ask you guys
I'm running newest RA-Amon Recovery
I'm running Damage Control 2.09.01
I have been TRYING to get A2SD working correctly for a few days now with no luck....
I've formatted my card, wiped my phone, partitioned SD as follows:
Swap 32mb
Ext 2 512mb (Changed to Ext 3)
Fat32 Remainder
Not sure if it matters, but I have a 32GB SD card...
When I run busybox df -h this is what I get:
C:\AndroidSDK\tools>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 4.0K 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 141.6M 28.4M 83% /system
/dev/block/mtdblock5 159.5M 67.1M 92.4M 42% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 457.4M 5.0K 433.0M 0% /system/sd
/dev/block//vold/179:1
30.7G 31.5M 30.7G 0% /sdcard
Also, if I try to install a program from Market, it downloads fine, but Fails to Install due to Insufficient Storage
If anyone has any ideas or would like me to try something else, I'm all ears. Phone starting to frustrate me

Don't know if this will work, but try this:
Go into an adb shell. Type this:
cd /data/data/com.android.vending/cache
rm -f *
reboot
This will clear the market cache and reboot your phone.
Let me know if that works.
kronik03 said:
Been searching tons of forums for answer, seems like no ones problem is quite like mine though, so...Time to ask you guys
I'm running newest RA-Amon Recovery
I'm running Damage Control 2.09.01
I have been TRYING to get A2SD working correctly for a few days now with no luck....
I've formatted my card, wiped my phone, partitioned SD as follows:
Swap 32mb
Ext 2 512mb (Changed to Ext 3)
Fat32 Remainder
Not sure if it matters, but I have a 32GB SD card...
When I run busybox df -h this is what I get:
C:\AndroidSDK\tools>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 4.0K 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 141.6M 28.4M 83% /system
/dev/block/mtdblock5 159.5M 67.1M 92.4M 42% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 457.4M 5.0K 433.0M 0% /system/sd
/dev/block//vold/179:1
30.7G 31.5M 30.7G 0% /sdcard
Also, if I try to install a program from Market, it downloads fine, but Fails to Install due to Insufficient Storage
If anyone has any ideas or would like me to try something else, I'm all ears. Phone starting to frustrate me
Click to expand...
Click to collapse

[Q] How to increase internal phone storage?

I know this is a total noob thing to be asking, but I have researched and tried out various solutions and am still running out of space on my internal phone storage. I've installed the CM6.1 Magpie on a partitioned 8GB SD card with all apps set to install to sd-ext. I partitioned off 1GB for sd-ext, which seems to have worked as I can see some apps installed there.
I think I must have it set up incorrectly or incompletely despite my best efforts, as from what I understand I should be seeing my internal phone storage as being larger than 91.75MB. It's a problem as I now only have 15MB free, and it seems to be causing phone crashes.
I followed my_former_self's cm6.1.0 ds guide with magpie successfully, as far as I can tell. I am not certain if I also need to be using Firerat's customMTD... Can anyone offer some advice? I've done a lot of searching, but the info is so fragmented that I'm at a bit of a loss. (fr'instance, on the customMTD page the version is 1.5.6., but in the download area I see there's a 1.5.8 version too...)
Thanks for any help or pointers to any threads!
Phone: T-Mobile G1
ROM: Magpie-DS-CM6.1
Recovery: Amon-Ra

Can you please go into a terminal session
(or use
Code:
adb shell
) and type
Code:
df -h
and send the output here?
Probably you have done right everything, but your internal space is used by data ...
Sent from my Gingerbread on Dream using XDA App

df -h
AndDiSa said:
Can you please go into a terminal session
(or use
Code:
adb shell
) and type
Code:
df -h
and send the output here?
Probably you have done right everything, but your internal space is used by data ...
Sent from my Gingerbread on Dream using XDA App
Click to expand...
Click to collapse
I managed to free up some space last night by using Titanium's "integrate updates into ROM". That resulted in me having to reinstall Google Maps, but it did free up some space.
Here's my disk space usage:
Code:
$ adb -s HT94PGZ05646 shell
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 55.0M 0 55.0M 0% /dev
tmpfs 55.0M 0 55.0M 0% /mnt/asec
/dev/block/mtdblock3 91.0M 90.8M 200.0K 100% /system
/dev/block/mtdblock5 91.8M 57.1M 34.7M 62% /data
/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 915.1M 79.9M 786.4M 9% /sd-ext
/dev/block/mmcblk0p2 915.1M 79.9M 786.4M 9% /cache
/dev/block/mtdblock4 27.0M 1.1M 25.9M 4% /dev/cache
/dev/block/vold/179:1
6.5G 404.6M 6.1G 6% /mnt/sdcard
/dev/block/vold/179:1
6.5G 404.6M 6.1G 6% /mnt/secure/asec
"SD card & phone storage" shows internal phone storage available space as 34.67MB now, which seems to match /data.
I'm pretty sure I have all the pieces, I just can't put them together So if I *have* done things right, how do I get the system to mount /data elsewhere?

Custom MTD is not applied correctly, you have still a cache device with a size of 27 MB, which is unused at the moment.
To apply Custom MTD you should
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
(probably mtd 91 2 would be better for you, because there are only 200kb free on /system)
then boot into recovery, do a nandroid+sd-ext or bart backup
then apply the recovery-v1.5.8-CustomMTD_S.zip
reboot to fastboot and do a
Code:
fastboot erase system -w
fastboot reboot recovery
then do a nandroid / bart restore
then flash the boot-v1.5.8-CustomMTD_S.zip
then reboot and you should be fine.

ah so!
AndDiSa said:
Custom MTD is not applied correctly, you have still a cache device with a size of 27 MB, which is unused at the moment.
To apply Custom MTD you should
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
(probably mtd 91 2 would be better for you, because there are only 200kb free on /system)
then boot into recovery, do a nandroid+sd-ext or bart backup
then apply the recovery-v1.5.8-CustomMTD_S.zip
reboot to fastboot and do a
Code:
fastboot erase system -w
fastboot reboot recovery
then do a nandroid / bart restore
then flash the boot-v1.5.8-CustomMTD_S.zip
then reboot and you should be fine.
Click to expand...
Click to collapse
That's reassuring, your solutions reads like the general instructions I found on the firerat customMTD thread. That thread was a bit confusing and I was worried about mixing & matching things, especially given that the latest versions didn't match the versions in the thread. I shall report back!

Definitely an improvement!
AndDiSa said:
Custom MTD is not applied correctly, you have still a cache device with a size of 27 MB, which is unused at the moment.
To apply Custom MTD you should
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
(probably mtd 91 2 would be better for you, because there are only 200kb free on /system)
then boot into recovery, do a nandroid+sd-ext or bart backup
then apply the recovery-v1.5.8-CustomMTD_S.zip
reboot to fastboot and do a
Code:
fastboot erase system -w
fastboot reboot recovery
then do a nandroid / bart restore
then flash the boot-v1.5.8-CustomMTD_S.zip
then reboot and you should be fine.
Click to expand...
Click to collapse
Excellent! I am now seeing 117MB for total space and 59.66MB free. However, I worry that this won't be enough in the future. Can you advise me on how to create more space? Or will it do so automagically?

mtdpartmap.txt not read?
AndDiSa said:
Custom MTD is not applied correctly, you have still a cache device with a size of 27 MB, which is unused at the moment.
To apply Custom MTD you should
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
(probably mtd 91 2 would be better for you, because there are only 200kb free on /system)
then boot into recovery, do a nandroid+sd-ext or bart backup
then apply the recovery-v1.5.8-CustomMTD_S.zip
reboot to fastboot and do a
Code:
fastboot erase system -w
fastboot reboot recovery
then do a nandroid / bart restore
then flash the boot-v1.5.8-CustomMTD_S.zip
then reboot and you should be fine.
Click to expand...
Click to collapse
Hm... I am not sure it is reading mtdpartmap.txt, as the /system partition seems to be the same size:
Code:
# cat /sdcard/mtdpartmap.txt
mtd 91 2
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 55.0M 0 55.0M 0% /dev
tmpfs 55.0M 0 55.0M 0% /mnt/asec
/dev/block/mtdblock3 91.0M 90.8M 200.0K 100% /system
/dev/block/mtdblock5 116.8M 57.1M 59.6M 49% /data
/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 915.1M 79.9M 786.4M 9% /sd-ext
/dev/block/mmcblk0p2 915.1M 79.9M 786.4M 9% /cache
/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache
/dev/block/vold/179:1
6.5G 807.9M 5.7G 12% /mnt/sdcard
/dev/block/vold/179:1
6.5G 807.9M 5.7G 12% /mnt/secure/asec
Any thoughts on that?

Hmm ... creating more internal space will be difficult, because the G1 has only 196MB
The only chance you have, if this isn't sufficient for you: use a2ext, i.e. put all applications to sd card and keep only the data ofthe applications on internal memory. I am doing so (~100 application installed) and normally I've still around 30MB free.
If that is still not sufficient for you, you can use data2sd. Firerat's all in one patch should work with your rom. Choosing the ddb option will move app data to sd-ext and will free internal space. Disadvantage of this option: if you have a slow sd card you will notice a performance decrease.

AndDiSa said:
Hmm ... creating more internal space will be difficult, because the G1 has only 196MB
The only chance you have, if this isn't sufficient for you: use a2ext, i.e. put all applications to sd card and keep only the data ofthe applications on internal memory. I am doing so (~100 application installed) and normally I've still around 30MB free.
If that is still not sufficient for you, you can use data2sd. Firerat's all in one patch should work with your rom. Choosing the ddb option will move app data to sd-ext and will free internal space. Disadvantage of this option: if you have a slow sd card you will notice a performance decrease.
Click to expand...
Click to collapse
Thanks for the info. I'm already using a2ext, as it's built into Magpie and I've locked app installations to ext in the cyanogen mod settings. However, if you're running 100+ apps and having no probs, I doubt I will either. Thanks again!

/datadata (/dev/block/mtdblock6) has 100 mb used (64 free) even after formatting

Hi
I'm using CM9 on SGS i9000 and after so many messages of low space, I found that /dev/block/mtdblock6 was almost full with 100 mb used even after deleting every single folder but lost+found:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 189444 32 189412 0% /dev
/dev/block/mtdblock2 256000 240312 15688 94% /system
/dev/block/mtdblock3 17920 2336 15584 13% /cache
/dev/block/mmcblk0p2 1935192 276228 1658964 14% /data
/dev/block/mtdblock6 176128 111872 64256 64% /datadata
/dev/block/mmcblk0p1 5913120 3036544 2876576 51% /sdcard
~ # cd /datadata
/datadata # ls
lost+found
/datadata # rm -R lost\+found/
rm: can't remove 'lost+found': Directory not empty
I've tried formatting from CWM but that folder is still there and it complains of being non empty but (a ls on it shows nothing)
¿How could I recover that phantom used space so my apps doesn't complain?
Thanks in advance

Found it!
Flashing a new image (stock one), then reflashing CM fixed it, it appears that the problem was just with the FS and not with the flash memory.
It's a pitty than CWM format option did not fixed it :/
But at least it works

Hi,
Glad you fix your issue, can I barrow your thread? The issue is not exactly the same (at least I think) but the title fit so well with the problem and it is in the good category/section.
I have 60mb of unused/unusable/missing space in /datadata.
If I compare the result of command DU vs DF I got a difference of 59M for what is supposed to be the space “used”.
Command: du -sch /datadata
Result: 104.1M /datadata
Command: df /datadata
Result:
Filesystem Size Used Free Blksize
/datadata 172M 163M 8M 4096
The application DiskUsage give me a mysterious “System Data” of 62Mb.
Lost+Found folder is empty but I cannot delete it. Thought I don’t think it’s the issue... Lost+Found folder was showing up with DiskUsage when I got corruption on my emmc. So the situation is different.
I manage to put e2fsck in bin, but my adb don’t connect in download mode… and when the system is up it is impossible to umount “/dev/block/mtdblock6 /datadata yaffs2 rw,relatime 0 0” and neither it is to scan it with e2fsck.
I would like to find a rapid fix for that in case it would re-occur in the future. If we don’t find one I will probably Reset Data/Factory and wipe everything before flashing the rom again and restore with Titanium…
Searching for this issue always lead to either LOST.DIR LOST+FOUND or format, but everybody seems to have that issue on sdcard which is easier to move data,format then move data back…
Is there somebody else have this issue on /datadata? Do you think it may be fix by e2fsck? If yes then how can I run it? Do you have any idea on how to fix that?
Thanks you,
Model : GT-i9000M
Rom : CM9 nighties
Kernel : CM9 stock or Semaphore
Others :
- Restoring with Titanium backup if necessary (did not since a while)
- Using Wendigogo Datafix http://forum.xda-developers.com/showthread.php?p=26375859
EDIT: Welcome to this forum. At least now your first 2 post have an reply

That goes way over my skill.
Can somebody adapt this to our i9000?
http://forum.xda-developers.com/showthread.php?p=17752957
The e2fsck I have is coming from that zip. I can try to adapt in the script all /dev reference to our phone. But even with that, I think there a part that need to be compiled no? I don't know anything about these binary that are used for CW....
Edit : let me guess, YAFFS file system cannot be fix by e2fsck?! Anyway, if that could not help for my specific issue maybe it can be useful for other situations...
Envoyé depuis mon GT-I9000 avec Tapatalk

Silentbob999 said:
That goes way over my skill.
Can somebody adapt this to our i9000?
http://forum.xda-developers.com/showthread.php?p=17752957
The e2fsck I have is coming from that zip. I can try to adapt in the script all /dev reference to our phone. But even with that, I think there a part that need to be compiled no? I don't know anything about these binary that are used for CW....
Edit : let me guess, YAFFS file system cannot be fix by e2fsck?! Anyway, if that could not help for my specific issue maybe it can be useful for other situations...
Envoyé depuis mon GT-I9000 avec Tapatalk
Click to expand...
Click to collapse
I was not able to find on Linux any repairing tool, that's why I finally used a full image restore and repartition to have the FS recreated and usable again... CWM, CM9 and TitaniumBackup did the rest...

is that ok for you if I try to get support by using your thread or you prefer that I create a new one for my problem ?
For recap: I try to understand why /datadata is always full while CM9 is suppose to clean cache in there automatically. I think this is coming from that mysterious "System Data" that now taking 64.1Mo on my /datadata partition. That seems to correspond with the difference between result given by DU and DF command.
Code:
DF (153220) - DU (91836) = 61384 (59.9Mo)
Code:
***************************
* DU result *
***************************
Result of Data usage
Total : 172.5M (176656)
Data/data : 80.5M (82420)
Datadata : 89.7M (91836)
Libs Total : 41.2M (42144)
Libs in /Data/data : 38.2M (39080)
Libs in /Datadata : 0 (0)
Cache Total : 69.6M (71247)
Cache in /Data/data : 35.9M (36784)
Cache in /Datadata : 33.7M (34467)
Databases Total : 30.9M (31657)
Databases in /Data/data : 5.4M (5544)
Databases in /Datadata : 25.5M (26137)
Free space in /datadata : 83164
***************************
* DF result *
***************************
Filesystem Size Used Free Blksize
/datadata 172M 149M 22M 4096
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock6 176128 153220 22908 87% /datadata
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock6 172.0M 149.6M 22.4M 87% /datadata
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/block/mtdblock6 172 150 22 87% /datadata
***************************
*** TYPES ***
***************************
1206 - app_appcache
3969 - app_databases
23432 - files
31681 - databases
39080 - lib
71251 - cache
***************************
*** Cache ***
*** TOP 20 ***
***************************
44 /datadata/com.smartandroidapps.audiowidget/cache
61 /datadata/com.google.android.youtube/cache
72 /data/data/ca.lapresse.android.lapressemobile/cache
72 /data/data/com.aurorasoftworks.quadrant.ui.standard/cache
96 /datadata/com.mikersmicros.fm_li/cache
112 /data/data/com.mobilityflow.torrent/cache
152 /data/data/com.pelmorex.WeatherEyeAndroid/cache
1617 /datadata/com.eolwral.osmonitor/cache
3106 /datadata/com.estrongs.android.pop/cache
4692 /data/data/com.artelplus.howtotie/cache
4692 /data/data/com.et.easy.download/cache
4704 /data/data/com.koushikdutta.rommanager/cache
4724 /data/data/os.tools.scriptmanager/cache
5139 /datadata/com.android.vending/cache
5713 /datadata/ccc71.bmw/cache
5713 /datadata/com.aor.droidedit/cache
5724 /data/data/com.unit.convert/cache
5760 /data/data/ds.cpuoverlay/cache
5972 /data/data/com.android.email/cache
12532 /datadata/com.quoord.tapatalkpro.activity/cache
***************************
*** Database ***
*** TOP 10 ***
***************************
615 /datadata/com.android.providers.telephony/databases
634 /datadata/com.google.android.apps.plus/databases
823 /datadata/com.google.android.apps.docs/databases
1168 /datadata/com.android.providers.contacts/databases
1379 /datadata/dk.tacit.android.foldersync.full/databases
1532 /datadata/com.dropbox.android/databases
3354 /datadata/com.kiragames.unblockmefree/databases
4315 /datadata/com.android.email/databases
5520 /data/data/ca.lapresse.android.lapressemobile/databases
6404 /datadata/com.android.providers.media/databases
***************************
***************************

Silentbob999 said:
is that ok for you if I try to get support by using your thread or you prefer that I create a new one for my problem ?
For recap: I try to understand why /datadata is always full while CM9 is suppose to clean cache in there automatically. I think this is coming from that mysterious "System Data" that now taking 64.1Mo on my /datadata partition. That seems to correspond with the difference between result given by DU and DF command.
Code:
DF (153220) - DU (91836) = 61384 (59.9Mo)
[/CODE]
Click to expand...
Click to collapse
From my understanding /datadata should not be always full, and even if cache is supposed to be cleaned automatically, system will complain if under some MB theresold.
If DU + DF != Total then you may have the same problem I had (reported at dmesg as corruption or failing NAND) which was marking blocks as bad /unusable thus consuming the available disk space.

lost+found
thatś the problem
lost+found directory
i try to see inside with ls -l command
there was plenty hidden files
it was for me quite difficult to dellete all
at last i managed to clean nearly everything
now i have just lost+found directory with aparently no files
but imposible to delete directory
my whole sd card is 3 gb and was fully occupied by this lost+found
if possible the best solution should be to format this sd card....but i don t know how...
thanks