Database Users

[Q] question about cache partition.. and system

Ok, now im wondering, is the cache directory in system supposed to be connected to the cache partition that gets flashed in some roms?
For example, say i look at my root dir on my phone, i go to data and it lists the used and free which combined, is the auto sized amount of my data partition, if i go to system,the used and free combined is tha size of teh system partition i have (i used cwm and in my case its 410M) now i flashed a cache partition (of 10M) so i had assumed that the cache dir in root was linked to my cache partition, so the amount used/free combined would be 10M, but instead its the same size as of my data partition.. so i know that its using that partition instead..
is it supposed to be like that?
what use is the cache partition?
also, does anyone think there would be a benefit if the system partition was in ext3 format instead of yaffs? i know that most oem roms come with the system partition set in ext3 format, would that ever be possible with magldr?
thanks.

Anybody got 2 cents they can throw in?

cmon, any answer at all would be nice from anyone..

It looks normal to me. Most sense builds i saw here, dont use the cache partition, instead the data partition is used. So basically you could flash a 1mb cache partition and it will work and you get some more space for system.
btw, on nand there is allways yaffs used for system, not ext(X).

Use of cache partition are depended on the Android Builds. Most builds do not use cache partition at all. /cache is redirected to /data/cachemnt on the userdata partition. However cache partition is required for CWM. It will compliant if cache partition is missing.
ext2/3/4 are not suitable for NAND Flash. YAFFS2 is develop for and more suitable for NAND Fash Device. However, there are ways to use ext2/3/4 though other methods. (one of them being loop device mount) and for Read Only. Each method has its pros and cons. it really depend if the benefits outweights its drawbacks.

greg17477 said:
It looks normal to me. Most sense builds i saw here, dont use the cache partition, instead the data partition is used. So basically you could flash a 1mb cache partition and it will work and you get some more space for system.
btw, on nand there is allways yaffs used for system, not ext(X).
Click to expand...
Click to collapse
hey first, THANK YOU for commenting. ok, thats interesting, i have always seen it suggested to use a 10 -40 mb cache partition, ive also heard that market can have some weird effects such as not being able to download if the cache partition was too small.. thats why i assumed that it was used by the system in some way
nightcraw said:
Use of cache partition are depended on the Android Builds. Most builds do not use cache partition at all. /cache is redirected to /data/cachemnt on the userdata partition. However cache partition is required for CWM. It will compliant if cache partition is missing.
ext2/3/4 are not suitable for NAND Flash. YAFFS2 is develop for and more suitable for NAND Fash Device. However, there are ways to use ext2/3/4 though other methods. (one of them being loop device mount). Each method has its pros and cons. it really depend if the benefits outweights its drawbacks.
Click to expand...
Click to collapse
i asked that since i have seen most of the oem roms using ext3 and assumed it offered some benefit speed-wise. all phones use nand of the same type yeah? so whats the benefit of using ext3 when yaffs2 preforms much better on it?

Nandroid won't backup my ext4 partition?

I'm currently using data2ext with B 0.8, and I have a 2gb ext4 partition. I tried performing a backup using BlaY0's "Customized CWM 3.0.1.3 fake-flash with ext4 support". However, I get a message saying something along the lines of "Couldn't mount sd-ext. Sd-ext backup may not be supported on this device."
Any ideas? Is it unable to backup a ext partition larger than 1gb? Is there any alternative to a nandroid backup?
EDIT: Damn, is this cause I cheated when partitioning the SD card?

I guess the problem is in ext4 feature huge_files. Even tho my customized CWM has ext4 support, it lacks huge files support (files over 2TB). This feature however is set by default when formatting ext4 partition. It can be turned off using tune2fs. Consult mr. Google on how to use tune2fs.
Sent from my HTC Legend

i tried turning off huge_file support but i still cant nandroid the ext4 partition created with the customised fake flash.
from adb shell in latest CWM recovery i tried:
tune2fs -O ^huge_file /dev/block/mmcblk0p2
/data/data/com.koushikdutta.rommanager/files/e2fsck -fpDC0 /dev/block/mmcblk0p2
Click to expand...
Click to collapse
then rebooted but still not love with nandroid mountind the ext4 partition

fixed my problem:
i had reverted to using CWM 2.5.0.7 gui / update.zip which does not support ext4
so going back to blay0's custom update.zip (3.0.1.3) I can now nandroid backup my ext4 partition. (i have still got huge_files turned off as per above)
Just dunno how to use blay0s version with rom recovery gui, but no biggie

CWM 2.5.1.8 MZ - wipe problem

Hi,
I cant mount and wipe :
/data - it write : cant mount /dev/block/stl7
/cache - it write : cant mount /dev/block/stl8
/dalvik-cache - it write : cant mount /dev/block/stl7 (File exists)
it does not matter if I have JPQ or JPS, deodexed or stock - problem i same ...
any tips ?

Delete all partitions from your sdcard, format it (not in CWM, with a 3rd part program) and then re-create partitions (from CWM).

andreapier said:
Delete all partitions from your sdcard, format it (not in CWM, with a 3rd part program) and then re-create partitions (from CWM).
Click to expand...
Click to collapse
I did this already and it does not helped as it result to this state
I created partitions with CWM included at Kyrillos 7.0
I checked there are no difference at this CWM and CWM included at Kyrillos.
But I get same issue when I used later stock ROM and deodexed too with G3MOD 1.7 kernel. There was first time I see wipe issue ...
Now I am trying gparted, we will see. ..

OK, tested, I exactly did it like You said and unfortunatelly it does not work, I get same results :-( ... and what worst I will ahve to again move 32 GB of data -**** :-(
any other tips ? different kernel usage etc ?
thnaks for any help ...

radek.god said:
OK, tested, I exactly did it like You said and unfortunatelly it does not work, I get same results :-( ... and what worst I will ahve to again move 32 GB of data -**** :-(
any other tips ? different kernel usage etc ?
thnaks for any help ...
Click to expand...
Click to collapse
when i had this problem once, the filesystems were gone from EXT2 / EXT4 to RFS after flashing a new rom.
i don't know which filesystems u use...
have a look into /sdcard/Android/data/g3mod/fs.current , if u use g3mod kernel. (for fugumod kernel it's /sdcard/Android/data/fugumod/fs.current)
put a file "fs.convert" in /sdcard/Android/data/g3mod/ (or .....fugumod/)
the file looks like attached... (!!! cut off .txt extension !!!)
after that you have to reboot (!!! not into CWM !!!) and WAIT PATIENTLY for the kernel to convert the filesystems.
After that you should have no problems anymore with the CWM recovery.
good luck!

/data + /cache deleted - pfeeeeeeeeeeeeee !
ufff,
as noone knows and nothing work, I tried some stupidity
I changed permission to /data and /cache and tied delete them manually (mean after it there were no /data and no /cache directory.
NO flash JPS helps, no wipe data helped , I though phone were to the hell , as I always stucked at screen lock , then I see some error message setup cant process, forced closure and phone restart .over and over again
I tried flash Kyrillos 7.0 OC and it works - I am back inj game again
anyway I think there have to be made some changes to CWM, because :
- Kyrillos ROM -all wipes and mounts work
- G3 MOd kernel - wipes and mounts does NOT work correctly
- other kernel after apply CWM - wipes and mounts does not work correctly

as i told you: after flashing JPS all filesystems are converted to rfs
you can also use g3modAPP to change it (only under g3 kernel i think)

mankokoma said:
as i told you: after flashing JPS all filesystems are converted to rfs
you can also use g3modAPP to change it (only under g3 kernel i think)
Click to expand...
Click to collapse
what does it means to me ? - as Kyrillos 7.0 is JPS based too ...
If I will convert rfs to efs (?) will CWM work to me even at JPS ?
what partitions have to be converted to make CWM works ?
If Kyrillos use rfs too, can be CWM files riped backward from Kyrillos ROM /system to stock/deodexed JPS ?
I need JPS stock + fugumod ultra + 5lockscreen_extended menu + CWM
And I tried CWM at JPQ , same issue - cant mount /wipe

mankokoma said:
as i told you: after flashing JPS all filesystems are converted to rfs
you can also use g3modAPP to change it (only under g3 kernel i think)
Click to expand...
Click to collapse
Ok, I will try, I did no tee your post because of some page error (my side ) thanks

if u use STOCK rom there is NO CWM.
Even NOT if u use fugumod kernel.
CWM is included in custom ROMs e.g. Kyrillos' ROM
and in G3mod kernel.
If u want to have CWM you must use one of both.
When u have flashed a stock rom, the filesystems are converted to RFS.
Look into above attached file and u will see what is usually used for partition filesystems.
mmcblk0p2 ext4 (external sd-partition)
stl6 ext2 (/system)
stl7 ext4 (/data)
stl8 ext2 (/cache)
Further, when u wanna use the external partitions on the sdcard u have to use Kyrillos' app2sd script in /etc/init.d
To convert the filesystems is a just suggestion - it should also work with RFS (though i'm not sure about that....)
but you have to look at /sdcard/Android/data/fugumod/fs.current to see what filesystems are used.

mankokoma said:
if u use STOCK rom there is NO CWM.
Even NOT if u use fugumod kernel.
CWM is included in custom ROMs e.g. Kyrillos' ROM
and in G3mod kernel.
If u want to have CWM you must use one of both.
When u have flashed a stock rom, the filesystems are converted to RFS.
Look into above attached file and u will see what is usually used for partition filesystems.
mmcblk0p2 ext4 (external sd-partition)
stl6 ext2 (/system)
stl7 ext4 (/data)
stl8 ext2 (/cache)
Further, when u wanna use the external partitions on the sdcard u have to use Kyrillos' app2sd script in /etc/init.d
To convert the filesystems is a just suggestion - it should also work with RFS (though i'm not sure about that....)
but you have to look at /sdcard/Android/data/fugumod/fs.current to see what filesystems are used.
Click to expand...
Click to collapse
many many many ..... THAAAAAAAAAAAAAAAAAAAAANKS
I have stock NON deodexed and CWM works after conversion
I had no proble mount all and wipe all
I have ext4 as sd-ext

solution
bro if ur using g3mod then just convert all filesystems to ext2 using g3mod app ..............................its tested n m pretty sure tat it'll work

varunrocks17 said:
bro if ur using g3mod then just convert all filesystems to ext2 using g3mod app ..............................its tested n m pretty sure tat it'll work
Click to expand...
Click to collapse
no, I am using Fugumod 1366 only, I get best results and most stable instead of G3MOD kernel 1.6 and 1.7
but I am not sure about ext2 vs ext4 someone test it on PC and ext2 get better speed results

Check your file system partitions

I recently flashed the new 4EXT Mod of ClockworkMod Recovery. The 4EXT Recovery is based off of Koush's CWM Recovery but offers additional power options, one of which is the ability to show the file system format your partitions are formatted in. To my surprise my system was formatted in the Ext 4 format and my data and cache partitions were formatted in Ext 3. The new 4EXT Recovery offers the option to convert the format without deleting any of the data. Your ROM will stay intact after the conversion. I selected that option and changed my data and cache partitions to ext 4 to match my system, rebooted, and notice quite an improvement in speed and smoothness in my current CM7 Nightly. After looking into it further I found out that the SuperwipeG2 that many of us have been flashing is formatting our partitions in the Ext 3 format. The reason only my system was formatted in ext 4 is because I used ClockworkMod Recovery the last time I did a full wipe to first flash the Superwipe, and then I immediately formatted system again with ClockworkMod Recovery. If you've used SuperwipeG2 to do a wipe, more than likely your system, data, and cache partitions are now Ext 3. You might want to check with your ROM developer to see if your ROM will run on the Ext 4 format. If its a CM7 based ROM, it will.
You can find more information about the Ext 4 format here.
Tsubus has since modified SuperwipeG2 so that it now formats the partitions into ext 4 when you flash it. I've used it and it also includes the EFS wipe. You can find it here. As I said, if there is no reason to wipe right now the new 4EXT Recovery can convert your partitions if you choose if they are in currently Ext 3. At the very least you can see what format they're currently in with 4EXT. I highly recommend it. You can always flash back to CWM Recovery if and when you choose. The partitions will remain Ext 4 once you choose to convert.
UPDATE: Several users have reported that checking partition information with Terminal Emulator is not reliable.

i just caught this issue this morning as well, all my partitions are in ext3, going to convert today. thanks for this post and the links to the new superwipe! +1
Sent from my HTC Vision using xda premium

Thanks for pointing this out. I have all of mine in ext3 right now and plan on converting to ext4 here in a minute.

if ive never used superwipe my partitions are still in EXT4?

nonione said:
if ive never used superwipe my partitions are still in EXT4?
Click to expand...
Click to collapse
Probably yes, but it wouldn't hurt to check. The new 4EXT Recovery will display your current partition status. Then you'll know for sure.
Sent from my HTC Vision using xda premium

So could someone clarify my understanding of this? If we are currently using ext3 we have 2 options to move to ex4 and keep CWM:
1) keep CWM, use the new superwipe+ext4, flash cm7
2) switch to 4ext recovery, convert fs to ext4, go back to CWM recovery
Alternatively, I would consider switching to 4EXT recovery permanently, but I am a bit reluctant to ditch CWM just because I'm so used to it. Is it worth the switch?

c00ller said:
So could someone clarify my understanding of this? If we are currently using ext3 we have 2 options to move to ex4 and keep CWM:
1) keep CWM, use the new superwipe+ext4, flash cm7
2) switch to 4ext recovery, convert fs to ext4, go back to CWM recovery
Alternatively, I would consider switching to 4EXT recovery permanently, but I am a bit reluctant to ditch CWM just because I'm so used to it. Is it worth the switch?
Click to expand...
Click to collapse
ClockworkMod is using the Ext 4 format. Its just that currently there is no way to tell what format your partitions are formatted in with CWM. If you flash the SuperWipeG2+ext4 from tsubus with CWM and don't ever use the original Superwipe and don't restore a backup, you're all set and done. BUT, if you restore a backup created by CWM that was partitioned at the time you created the backup in Ext 3, you'll be back to Ext 3 again. IE you've got to scrap all your old backups....all of us do if we want to stay with Ext 4. So, if you're willing to do a full wipe with the new SuperWipeG2+ext4 and CWM, you're good to go.
edit: yes to your number two. You can convert your Ext 3 partitions to Ext 4 with the new 4EXT Recovery and then go back to CWM. As I said above, after you do this you need to get rid of the original Superwipe and not restore old backups made in the Ext 3 format.
Sent from my HTC Vision using xda premium

I think I've just made the switch to 4EXT, it was very painless and I like the features of the recovery. Now I'm wondering, with the 4EXT recovery, do we still need the superwipeg2 zips (including the new, ext4 modified one)? Also, is there a thread with discussion about the SuperWipeG2+ext4.zip (i.e., where did you find the link to download it)?

c00ller said:
I think I've just made the switch to 4EXT, it was very painless and I like the features of the recovery. Now I'm wondering, with the 4EXT recovery, do we still need the superwipeg2 zips (including the new, ext4 modified one)? Also, is there a thread with discussion about the SuperWipeG2+ext4.zip (i.e., where did you find the link to download it)?
Click to expand...
Click to collapse
Use the new Superwipe just like you did and when you needed the old one. Tsubus modified it to format the partitions in ext 4. You can find his thread in the Development section. Its the CM7 ILWT thread. He modified the Superwipe right befor he went away for the weekend. The original link is in the OP of that thread. Be sure and hit his "thanks" button.
Sent from my HTC Vision using xda premium

Thanks very much for the info and links, Ed. I will make the switch and give you a proper 'thanks' later tonight.
Sent from my HTC Vision using XDA App

typing the following in terminal
Code:
mount
will tell you what filesystem types like ext2 ext3 ext4 etc, so u dont really need the other recovery to check if you're using ext3.
Code:
/dev/block/mmcblk0p25 [B]on /system type ext4 [/B](ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p26 [B]on /data type ext4 [/B](rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p27 [B]on /cache type ext4 [/B](rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p28 [B]on /devlog type ext4 [/B](rw,nosuid,nodev,noatime,barrier=1,data=ordered)
Still, I never even noticed that it was formatted as ext3 until i saw your post. Used the new superwipe and a fresh cm7 nightly. Everything flies now! Thanks for noticing the issue

Just checked via terminal emulator and mine are all in EXT4. Never used Superwipe before so I guess that's why.

sephiroth1439 said:
Still, I never even noticed that it was formatted as ext3 until i saw your post. Used the new superwipe and a fresh cm7 nightly. Everything flies now! Thanks for noticing the issue
Click to expand...
Click to collapse
Glad it worked out for you.

sephiroth1439 said:
typing the following in terminal
Code:
mount
will tell you what filesystem types like ext2 ext3 ext4 etc, so u dont really need the other recovery to check if you're using ext3.
Click to expand...
Click to collapse
martonikaj said:
Just checked via terminal emulator and mine are all in EXT4. Never used Superwipe before so I guess that's why.
Click to expand...
Click to collapse
WARNING: Ptesmoke and Ditamae have reported that this method wasn't accurate for them. Results reported by terminal emulator didn't match the actual file system ext's when they booted into 4EXT Recovery. After converting they have both posted that they noticed an improvement in performance.

Strange... so I checked thru Terminal and all partitions were EXT4, but after flashing the 4EXT Recovery and booting into recovery I discovered that data and cache were in fact EXT3. Hmm... I'm converting now, at any rate. Thanks again, Ed.

Just to clarify...
So the original Superwipe changes our partitions to ext3, and the new Superwipe up above changes/keeps it at ext4.
If that is correct it seems like we should remove the other instances of the original Superwipe in the forum and switch everyone over to the new Superwipe. What does reformatting via CWM change the file system to?

Nospin said:
Just to clarify...
So the original Superwipe changes our partitions to ext3, and the new Superwipe up above changes/keeps it at ext4.
If that is correct it seems like we should remove the other instances of the original Superwipe in the forum and switch everyone over to the new Superwipe. What does reformatting via CWM change the file system to?
Click to expand...
Click to collapse
Yes, the original Superwipe changes the partitions to Ext 3. I'm not sure if there are other ROMs out there doing the same thing. It depends on the scripting. Many ROMs are scripted to format the partitions first when you flash them. If users reading this thread take the information and post it to their ROM thread in the Development section of the forum that would help to get the news out to check to see if their partitions are formatted correctly.

Thanks OP! I used (my new friend) 4EXT Recovery and converted my data and cash partitions to ext4, got rid of my old SuperWipe and Dow loaded the new Superwipe.
CM7 does indeed seem smoother, and overall a bit faster.
Big thanks for the heads up!
Sent from my HTC Vision using xda premium

Also noticed the "eccentricity" of my /data and /cache being ext3, conversion to /ext4 was painless and the phone does seem to be running more smoothly.
(Then again, I utterly love this recovery--so powerful, and yet so simple to use )
Aaaand interestingly, at least if ROM Manager is any guide, they've finally pulled the 5.0.0.x "Seppuku Builds" of CWM. Which is nice, but 4EXT has sold me

I have a question that maybe someone in this thread could answer. As I said previously, I flashed the 4EXT Recovery last night and changed my data and cache from ext3 to ext4. Afterward, I noticed that my internal memory usage had decreased by approximately 70Mbs. Is this a result of less fragmentation? I'm assuming it's just a benefit of the way fourth extended filesystem works. Can anyone confirm this? Thanks in advance.

Purity rom f2fs

I was considering attempting to use the f2fs filesystem that is discussed in original android development but I'm a bit confused with what to do to load a new rom. Can anyone explain if it will work with the purity rom and what I need to do to get it working? Or also let me know if its not possible.

Yes, I have used Purity with F2FS, but this filesystem is unstable because the system hangs usually (I have also tried with SlimKat and RastaKat with same hangs copying many files).
Basically:
- You must flash "twrp-unofficial-2.7.1.0-f2fs.img" as a normal recovery and change /data, /cache and /system (optional) to F2FS.
You will find this option under Wipe -> Advanced Wipe, then select only one partition and press the "Repair or Change File System" button for change to F2FS. Use Wipe -> Format Data also (you will lost data in /sdcard).
- Install Purity ROM (if /system is converted to F2FS, you must use "convert2F2FS.jar" for modify ROM zip and must install this new ROM).
- If /system is F2FS, install "KTManta_F2FS-26-06-2014-ALLF2FS.zip" Kernel or "KTManta_F2FS-26-06-2014_CACHE_DATA_PARTITIONS.zip" else.

patzzz said:
Yes, I have used Purity with F2FS, but this filesystem is unstable because the system hangs usually (I have also tried with SlimKat and RastaKat with same hangs copying many files).
Basically:
- You must flash "twrp-unofficial-2.7.1.0-f2fs.img" as a normal recovery and change /data, /cache and /system (optional) to F2FS.
You will find this option under Wipe -> Advanced Wipe, then select only one partition and press the "Repair or Change File System" button for change to F2FS. Use Wipe -> Format Data also (you will lost data in /sdcard).
- Install Purity ROM (if /system is converted to F2FS, you must use "convert2F2FS.jar" for modify ROM zip and must install this new ROM).
- If /system is F2FS, install "KTManta_F2FS-26-06-2014-ALLF2FS.zip" Kernel or "KTManta_F2FS-26-06-2014_CACHE_DATA_PARTITIONS.zip" else.
Click to expand...
Click to collapse
Where do you get convert2F2FS.jar?

Using f2fs with omnirom. All partition were formatted with f2fs. Having no issue with last update. You will find all resources in my thread