Related
I will get an email ill delete it but it will not delete from the browser/email it self and it will show me that i still have messeges unread and i have to go on the computer on the browser to delete them. someone please help!!!
bump bump please help
Did you try deleted the db for it? I heard from others that worked for them. I had that issue. I finally just reset everything. But first, go into applications, select Gmail, and delete databases and preferences.
i did that .. there was 2 gmail things so deleted *clear data* on both of them. will see if that works. thank yoU!
clearing data dont work.. still shows 12 kb and dont go away..
someone can help please? im missing 1 meb somewhere i guess. i have everything on the sd and only 71.
here is my df-h
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Smoku>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 48.4M 0 48.4M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 67.5M 65.5M 2.0M 97% /system
/dev/block/loop0 1.5M 1.5M 0 100% /system/modules
/dev/block/loop1 3.1M 3.1M 0 100% /system/xbin
/dev/mmcblk0p2 478.4M 133.3M 320.3M 29% /system/sd
/dev/block/mtdblock5 74.8M 3.0M 71.7M 4% /data
/dev/block/mtdblock4 67.5M 1.1M 66.4M 2% /cache
/dev/block/mmcblk0p1 7.0G 356.7M 6.6G 5% /sdcard
#
Pic 1:
So I have this 'red' miniSD icon notification on the upper right of my screen. (refer to attached pics).
Pic 2:
...and it says Low on Space etc...
Pic 3:
I click on the notification and it takes me straight to "Manage Applications."
Any idea what the heck is going on here? LOL
How do I correct this notification?
Note:
I checked the stock 2GB miniSD and the only thing on there was Avatar.
Everything seemed to be saving straight to the phone.
I just changed the stock 2GB card out to a 16GB.
Go to settings and sd card then scroll down and it should tell you how much memories you have for apps. How many apps do you have?
Sent from my SGH-T959 using XDA App
bauerlucas said:
Go to settings and sd card then scroll down and it should tell you how much memories you have for apps. How many apps do you have?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
App Storage:
1.50GB
Phone Storage:
Total space: 12.78GB
Available: 12.35GB
SD Card:
Total space: 14.63GB
Available: 10.15GB
As you can see, running out of space isn't the issue....I'm wondering if it could perhaps be a bug? Debating if I should just factory reset.
This is so strange........anyone????
My boss had the same issue with his myTouch slide, only fix was to master reset.
nacron said:
My boss had the same issue with his myTouch slide, only fix was to master reset.
Click to expand...
Click to collapse
Good to know, I was debating on doing that all day....was hoping for another solution haha....allll those appppppsss...oh well
By any chance have you applied the lag fix? Low memory reports are a common side effect of the lag fix.
MrGibbage said:
By any chance have you applied the lag fix? Low memory reports are a common side effect of the lag fix.
Click to expand...
Click to collapse
I haven't.
I've noticed that the readings in the settings for storage space is not accurate. I deleted 7GB's worth of videos off of my 16GB miniSD card and it still shows the same old reading that it was before. I checked "My Device," app and it shows the correct storage numbers...
I hope Froyo fixes all this...
If you are rooted, enable USB debugging and use ADB to enter the following commands
Code:
adb shell
su
busybox df -h
If you use terminal emulator you can drop "adb shell".
You should get an output like this:
Code:
$ su
su
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 162.8M 0 162.8M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/stl9 275.8M 248.2M 27.6M 90% /system
/dev/block/mmcblk0p2 1.9G 326.6M 1.6G 17% /data
/dev/block/mmcblk0p3 255.8M 72.8M 182.9M 28% /data_tmo
/dev/block/stl10 127.2M 48.8M 78.4M 38% /dbdata
/dev/block/stl11 30.1M 3.7M 26.4M 12% /cache
/dev/block/stl3 5.9M 4.0M 1.9M 68% /efs
/dev/block//vold/179:1
13.2G 6.7G 6.5G 51% /sdcard
/dev/block//vold/179:9
7.6G 2.0G 5.6G 26% /sdcard/sd
#
Code:
/dev/block/stl10 127.2M 48.8M 78.4M 38% /dbdata
is the important line. You might be using all your database storage, literally. I don't know how to clean it out, though.
raduque said:
If you are rooted, enable USB debugging and use ADB to enter the following commands
Code:
adb shell
su
busybox df -h
If you use terminal emulator you can drop "adb shell".
You should get an output like this:
Code:
$ su
su
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 162.8M 0 162.8M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/stl9 275.8M 248.2M 27.6M 90% /system
/dev/block/mmcblk0p2 1.9G 326.6M 1.6G 17% /data
/dev/block/mmcblk0p3 255.8M 72.8M 182.9M 28% /data_tmo
/dev/block/stl10 127.2M 48.8M 78.4M 38% /dbdata
/dev/block/stl11 30.1M 3.7M 26.4M 12% /cache
/dev/block/stl3 5.9M 4.0M 1.9M 68% /efs
/dev/block//vold/179:1
13.2G 6.7G 6.5G 51% /sdcard
/dev/block//vold/179:9
7.6G 2.0G 5.6G 26% /sdcard/sd
#
Code:
/dev/block/stl10 127.2M 48.8M 78.4M 38% /dbdata
is the important line. You might be using all your database storage, literally. I don't know how to clean it out, though.
Click to expand...
Click to collapse
Excellent info...I'll look into it..thanks!
http://forum.xda-developers.com/showthread.php?t=752471&highlight=Database+Storage+Low
Check out this thread.
If you click on the memory card you can delete the Contacts (should be bloated 60mb+) I did this two weeks ago and haven't had a problem since.
I had the same symptoms (red error message about the database). My web cache had bloated to 110MB. Deleted the cache today and so far so good.
talltexan said:
http://forum.xda-developers.com/showthread.php?t=752471&highlight=Database+Storage+Low
Check out this thread.
If you click on the memory card you can delete the Contacts (should be bloated 60mb+) I did this two weeks ago and haven't had a problem since.
Click to expand...
Click to collapse
x2.. same here
MrGibbage said:
I had the same symptoms (red error message about the database). My web cache had bloated to 110MB. Deleted the cache today and so far so good.
Click to expand...
Click to collapse
I have the same issue, but i'm unable to delete the cache. The browser always force closes when I try. Trying to clear it from Manage Applications doesn't do anything either.
Is there any other way to clear the browser cache? Thanks
You might want to try one of the cache clearing tools in the market. You have to be root though. The cache clearing tools did not work for me, but they do work for some people. I was finally successful deleting the cache from the browser settings, but apparently that is not working for you.
Worst case, you may have to factory reset.
MrGibbage said:
You might want to try one of the cache clearing tools in the market. You have to be root though. The cache clearing tools did not work for me, but they do work for some people. I was finally successful deleting the cache from the browser settings, but apparently that is not working for you.
Worst case, you may have to factory reset.
Click to expand...
Click to collapse
Thanks...tried all the cache clearing on the Market and they didn't work, but doing a 'Clear Data' instead of Clear Cache worked in Manage Applications. Now all is well again.
iflyabeech said:
x2.. same here
Click to expand...
Click to collapse
great! I just lost my contacts!
good thing i have a back up somewhere...
just see click the red mem card icon on the notification, then browse through the apps that are bloated with data, mine was samsung apps (after an update).. clear this data and you're back to ok.
Hi all, let me get right to it. I searched the related threads on this subject but still not much luck in fixing my issue.
I have had the message, "low on space" almost since installing Android 2.2.1 on my HTC HD2.
I'll keep it brief but I had my phone finally lock up while running windows 6.5, so I finally installed Android and briefly loved it until I realized it seems to have its own problems. Mainly the phone locks up after watching a minute or two of youtube video. Sometimes is locks up just playing around with other less intensive apps. It even says, text message rejected due to full memory. Is this a memory issue? Did I install Android right? When I run Advanced task killer it says I have 300M free. Do I have bad blocks maybe?
Anyway's I installed Android 2.2.1
Baseband version: 15.42.50.11u_2.15.50.14
Kernal version: [email protected] #2
Build number: JDMS 1.6.2
I used these Android files from Youtube tutorial:
HSPL3
4shared.xxx/zip/eX1enbYn/HSPL3_PKG.html
DFT
4shared.xxx/rar/zZ8yMupc/DFT_LEO_MAGLDR113_DAF.html
JDMS7 ROM i recommend
4shared.xxx/archive/Ughps3aT/jdms.html
I'm a novice and unlocking phones, but I did manage to get Terminal to scan my memory log:
$ df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 205.9M 0 205.9M 0% /dev
tmpfs 205.9M 0 205.9M 0% /mnt/asec
/dev/block/mtdblock1 146.0M 136.2M 9.8M 93% /system
/dev/block/mtdblock3 742.0M 695.3M 46.7M 94% /data
/dev/block/mtdblock2 40.0M 8.8M 31.2M 22% /cache
/dev/block/vold/179:1
31.2G 1.9G 29.3G 6% /mnt/sdcard
df: /mnt/secure/asec: Permission denied
/dev/block/dm-0 2.0M 132.0K 1.9M 6% /mnt/asec/org.androidwikipedia.history-1
/dev/block/dm-1 2.0M 816.0K 1.2M 39% /mnt/asec/com.shootinggames.bowman-1
/dev/block/dm-2 2.0M 104.0K 1.9M 5% /mnt/asec/com.rechild.advancedtaskkiller-1
/dev/block/dm-3 9.1M 7.4M 1.8M 80% /mnt/asec/com.facebook.katana-1
/dev/block/dm-4 8.1M 6.3M 1.9M 77% /mnt/asec/com.droidstudio.game.devil2-1
/dev/block/dm-5 2.0M 292.0K 1.8M 14% /mnt/asec/jackpal.androidterm-1
$
Not sure if this is any of this info is helpful, let me know if other info should be provided and I'll get it to you. Is my partion setup right? Should I install Ice Cream Sandwich?
I just need a working phone, that is stable and has everything working, I really want to avoid Windows 6.5, it was horrible.
Thanks in advance for your help.
You should really try the newer versions of Android, they don't have these problems.
Wysmyrane ze srajPoda Tacza 3G z użyciem oprogramowania Tapatalk
*update* I found my old text messages saved to my Sim card, I deleted those and reset and did a AD hardreset with aMagldr and still no luck. I had a buddy send me a text message and it was rejected.
I guess this Android nand version has some kind of text bug then?
Is there a ICS version that you recommend that is stable and has everything working?
After installing new CM ROM: http://forum.xda-developers.com/showthread.php?t=1779324
Most things function fine, with a few hiccups. However, any time the phone is rebooted, it goes back to default settings. As if it cannot save anything.
So I pulled this out of dmesg:
Code:
VFS: Can't find ext3 filesystem on dev mmcblk1p25.
Which corresponds to /data in /system/etc/fstab.
Could anyone give some insight into this? Would it be safe to format to ext3?
t1nk_2 said:
After installing new CM ROM: http://forum.xda-developers.com/showthread.php?t=1779324
Most things function fine, with a few hiccups. However, any time the phone is rebooted, it goes back to default settings. As if it cannot save anything.
So I pulled this out of dmesg:
Code:
VFS: Can't find ext3 filesystem on dev mmcblk1p25.
Which corresponds to /data in /system/etc/fstab.
Could anyone give some insight into this? Would it be safe to format to ext3?
Click to expand...
Click to collapse
Not sure what the problem is, but do not format it to ext3. If you format it, there's a chance you'll brick since the key of the partition will change, and our locked bootloader requires them to be at a specific setting. All the format options in the recovery are really rm -rf commands (just deletes everything) and don't really format at all.
I'd wipe data\factory reset (from cwm) and reinstall the rom. If that doesn't work, then go here and download Quarx's latest build for the Bravo or over to my PA thread and download its latest. You can use PA exactly like CM10 by disabling PA's hybrid UI. I know for sure that PA version works cause I used if for a month before flashing a 7 port I'm started working on yesterday.
Good luck
skeevy420 said:
Not sure what the problem is, but do not format it to ext3. If you format it, there's a chance you'll brick since the key of the partition will change, and our locked bootloader requires them to be at a specific setting. All the format options in the recovery are really rm -rf commands (just deletes everything) and don't really format at all...
Click to expand...
Click to collapse
I did find in /default.prop:
Code:
# ADDITIONAL_DEFAULT_PROPERTIES (From bootmenu/config)
...
# Forbid format of these partitions in mount menu (use only rm -r)
ro.cwm.forbid_format=/misc,/devtree,/config,/boot,/recovery,/pds,/system,/logo
Most of those are mounted with an "emmc" filesystem/module I've never heard of in linux.
I'd wipe data\factory reset (from cwm) and reinstall the rom. If that doesn't work, then go ... and download Quarx's latest build for the Bravo or over to my PA thread and download its latest. You can use PA exactly like CM10 by disabling PA's hybrid UI. I know for sure that PA version works cause I used if for a month before flashing a 7 port I'm started working on yesterday.
Click to expand...
Click to collapse
Unfortunately, installing any ROM fails to fix the issue. Tried PA first, got stuck in a bootloop. That leads me to believe ROMs will always require a working file structure.
I did however 'factory reset/wipe cache' from stock recovery (which claimed to format /data), load ROM, reset/wipe, reboot.
This did appear to solve the absence of /data mount. But it did not resolve the userdata persistence between reboots.
I found in /data/system/uiderrors.txt:
Code:
11/2/12 5:19 PM: No settings file; creating initial state
I tried changing some permissions via adb shell, but these were reset on reboot.
I suspect something with the init scripts is reseting something (it shouldn't be) on boot, however this is an area unfamiliar to me. I know some of those files are readable, I guess I'll have to just go through them line by line and see what makes sense....
CM 10-20120912-NIGHTLY-mb520
Build: cm_mb520_userdebug 4.1.1 JRO03L eng. quarx.20120912.233429 test-keys
Bootmenu v2.0-beta + Bootmenu JB Recovery v5.7.0-kobe
Didn't find anything conclusive in the parsable sections of init.* files, however I did notice that they often mount partitions and setup permissions.
On further digging into my phone, I saw that my *original* /data mount was still failing to function. Even though it has been repopulated under rootfs.
My output of mount:
Code:
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p21 on /system type ext3 (rw,relatime,barrier=1,data=ordered)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/loop7 on /pds type ext3 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
ramfs on /tmp type ramfs (rw,relatime,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,cod
tmpfs on /mnt/sdcard/.android_secure type tmpfs (rw,relatime,size=0k,mode=000)
If someone could paste their output (working ROM) for comparison, please.
This might help explain why my internal storage reads as 0Gb available, preventing Play store installs (I can force copy backups via adb).
At least I can enjoy JB so long as I don't reboot/power off.
From Quarx CM10 Custom Kernel Defy Plus 11\04 (running on a Bravo)
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk1p21 on /system type ext3 (ro,relatime,data=ordered)
/dev/block/mmcblk1p24 on /cache type ext3 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered)
/dev/block/mmcblk1p25 on /data type ext3 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered)
/dev/block/loop7 on /pds type ext3 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
ramfs on /tmp type ramfs (rw,relatime,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
Here's one option you could try -- fsck to repair the filesystem of any damage.
reboot into recovery
start adbd (Advanced->Start adbd)
open a terminal\command prompt (on PC...)
adb remount
adb shell
su
umount /data
e2fsck -fv /dev/block/mmcblk1p25
reboot and hope it worked
While a crappy option, have you tried flashing the sbf yet? If flashing the sbf two or three time in a row doesn't fix your issues then (probably) nothing will.
Being that the fs was never mounted:
adb shell
su
e2fsck -fv /dev/block/mmcblk1p25
And output:
Code:
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk1p25
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Which made me want to simply format. I don't know about "signatures", is there a blkid-like function under /system/bin? AFAICK init scripts only refer to /dev fs when mounting.
...have you tried flashing the sbf yet?...
Click to expand...
Click to collapse
In the course of events, yes, I did. This is how it went: from Bandroidx recovery + BravoX ROM (working fine), installed CM10 (w/o clearing anything, I was excited) managed to get a mostly working system w/o gapps. Not knowing it came with its own bootmenu, tried installing Bandroidx again. Led to bootloader error. Flashed fixed_bravo_sbf.sbf. Got CM back. Not sure when /data was corrupted...
I also have p4_kobe_umts_kobe_user_3.4.2-125_KOB_FFW-4_product-keys-ATT-US_ATT-signed.sbf, and noticed a size difference. If I go this route, should I try this one? Or fixed_bravo_sbf.sbf again? Thanks again for the input.
The umount command is just for safety . Here's the output from a working /data from CM10
Code:
[email protected]:/system/bin # e2fsck -fv /dev/block/mmcblk1p25
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
662 inodes used (0.80%)
50 non-contiguous files (7.6%)
1 non-contiguous directory (0.2%)
# of inodes with ind/dind/tind blocks: 83/4/0
32693 blocks used (9.91%)
0 bad blocks
1 large file
329 regular files
320 directories
0 character device files
0 block device files
1 fifo
0 links
1 symbolic link (1 fast symbolic link)
2 sockets
--------
653 files
There is a major difference between the full and fixed sbf. The fixed sbf only contains the bootloader and devtree (maybe ramdisk as well). The full sbf contains the full stock system. The fixed is mainly for those that accidentally flash a Defy boot.img or devtree.img when flashing or porting Defy roms.
While it sucks, it sounds like you just need to flash the full sbf and start over from scratch. I usually flash the sbf once every other month even if nothing is wrong (just makes me feel better).
From what you said above, /data was probably corrupted when you flashed CM10 without wiping data. Unless I'm flashing the same rom over and over again (when testing ports out, etc) I always do a factory reset when flashing. Its the safest way to go and you'll get better support from devs when you flash onto a blank slate (easier to debug since /data not being wiped is usually the cause of random bugs). It may have been from installing BandroidX Recovery since it uses the stock init scripts. Never install BandroidX Recovery. It is very obsolete and only useful if you plan on using BravoX, and even then you can use Defy 2nd-init recovery (just set it to boot to stock). More than likely it was from the non-wiped flash.
Flashing original .sbf worked! :victory:
Rooted, installed 2ndInitDefy, and backed up everything from there to sdcard.
/data now mounts correctly, and userdata persistence in CM10 is functional. :highfive:
Learn something new every day.
t1nk_2 said:
Flashing original .sbf worked! :victory:
Rooted, installed 2ndInitDefy, and backed up everything from there to sdcard.
/data now mounts correctly, and userdata persistence in CM10 is functional. :highfive:
Learn something new every day.
Click to expand...
Click to collapse
Glad to here you're not screwed :victory:. The best thing about the Bravo is you can fix it just like you do Windows -- if it breaks, just reinstall -- if you can't reinstall then its time for an upgrade cause ya broke it .
Hi,
I've been struggling for days installing any custom rom into my defy.
When I finally checked the log, I saw it interrupted with "no space left on device" about halfway through.
But there still is space, only 32% are in use (~100MB of~ 300MB).
/system just ran out of inodes.
Finally I succeeded after I removed most of the terminals in /etc/terminfo/* from the latest nightly before installing it. (CM10, 20130110, that is)
df -i /system
Filesystem Inodes Used Available Use% Mounted on
/dev/block/mmcblk1p21 1968 1915 53 97% /system
I don't understand, how come /system only has ~2000 inodes (typical should be ~10k)?
(I'm not the first owner, so I don't know what happened to the device before...I got it with some Vodafone branded firmware on it, but you never know..)
I'm afraid of simply formatting it, because bootmenu and recovery seem to be running from /system, and formatting might render the device nonfunctional.
How do I get back to a proper fs?
Is there a way to safely format /system?
Or should I better tune2fs?
Anyone seen this before?
Thanks,
mcr42
Ran out of inodes! ("No space left on device")
I seem to have the same problem. A few days after doing a fresh install of CyanogenMod7.2 + Googleapps, I start to get Gapps and other processes crashing all the time. Looking in the logfiles using "adb logcat -d" even immediately after bootup, it reports:
W/BatteryStats( 2274): Error writing battery statistics
W/BatteryStats( 2274): java.io.FileNotFoundException: /data/system/batterystats.bin.tmp (No space left on device)
and indeed I have lots of space, but no inodes left at all:
df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk1p25
130837 97898 32939 75% /data
df -i .
Filesystem Inodes Used Available Use% Mounted on
/dev/block/mmcblk1p25
1296 1296 0 100% /data
Can anyone suggest what's going on and how to fix it?
Thanks,
Richard
P.S. As a bit of background, I wonder if things have got messed up on an earlier install when a while back after using S2E to move most things to an ext4 partition on the SD card, I later used S2E to revert the system to normal, but it crashed half-way through the process. I believe that is sorted now as "mount" doesn't report looking for anything on sd-ext partition (which I have removed since anyway):
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p21 on /system type ext3 (ro,relatime,barrier=1,data=ordered)
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)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk1p24 on /cache type ext3 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered)
/dev/block/mmcblk1p25 on /data type ext3 (rw,nosuid,nodev,noatime,nodiratime,data=ordered)
/dev/block/loop7 on /pds type ext3 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
ramfs on /tmp type ramfs (rw,relatime,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
CM10 latest nightly is the unofficial late august build by sunnyqeen. If you have custom recovery, flash AROMA wiper (search) and fully wipe system, data and cache in ext4 and then immediately flash ROM and gapps.
Is there a way to increase the number of inodes on /data?
Following up my email, I've been looking through the full list of files on /data (the number closley tallies with the 1296 inodes available). There were quite a few (but not excessive number) of debug files in /data/system/dropbox which I've deleted to free up a few inodes. However 1296 inodes doesn't seem sufficient. Does this tally with what most people have on their Defy phones? Grateful if someone could connect to their phone and run the following:
adb shell df -i /data
I have seen there have been reports of ClockworkMod Recovery prior to version 6 corrupting inodes:
http://forum.xda-developers.com/showthread.php?t=2111734
Grasping at straws, could this be what is happening resulting in a loss of inodes?
(Rebooting to (Cyanmod) recovery mode on my phone reports "Bootmenu Recovery v5.0.6" - does that tie in with CWM v5 then?)
Richard