i am currently runnning HERO ROM , if i back Up my sd card and re partition my sd card for 96MB linux swap , do i have to re flash the rom over ?
also im doing this because i hear runninq a 96MB linux swap , makes the Hero rom run smoother nd faster , any truth to this before i re partition ?
also any inputs?
thnx
next time Q&A, 96 from what i hear is good but starts to lag after a while. also if you just re-partition the linux-swap then you shouldn't have to flash the rom, but if you do ext3 as well then you should re-flash the rom
Rather then repartition, just resize your partitions. In Gparted use the Resize command. Take 64mb off your first partition, then move the starting point of the second partition back 64mb. Then add the 64mb to your swap. I do it all the time to experiment with different swap sizes. So far 96mb is the best in my opinion.
I got a shiny new class 6 16GB sd card. I partitioned it at about 15.5GB fat32 and 512 ext2, using the info in cyanogen's wiki: http://wiki.cyanogenmod.com/index.php/Apps2SD_On_CyanogenMod
From there I did the ext3 and then the ext4 updates.
Although I've searched for answers for a few hours now, I've been unable to determine why the device slows to a crawl at each point of user interaction at this point. Even unlocking the screen can time out...
I backed out the changes and copied the apps back over to internal storage and everything is zippy again, so at this point I am looking for suggestions. One thing I noticed was that when I used parted to delete the ext partition so the apps wouldn't go back to the card on the next boot, it still listed the ext partition as ext2. Can someone running ext3 or 4 let me know whether parted lists their partitions as such or if they are always reported as ext2?
What other techniques should I try? I would very much like to make this work as I get constant low-space warnings in my current setup. Thanks.
jasper1 said:
I got a shiny new class 6 16GB sd card. I partitioned it at about 15.5GB fat32 and 512 ext2, using the info in cyanogen's wiki: http://wiki.cyanogenmod.com/index.php/Apps2SD_On_CyanogenMod
From there I did the ext3 and then the ext4 updates.
Although I've searched for answers for a few hours now, I've been unable to determine why the device slows to a crawl at each point of user interaction at this point. Even unlocking the screen can time out...
I backed out the changes and copied the apps back over to internal storage and everything is zippy again, so at this point I am looking for suggestions. One thing I noticed was that when I used parted to delete the ext partition so the apps wouldn't go back to the card on the next boot, it still listed the ext partition as ext2. Can someone running ext3 or 4 let me know whether parted lists their partitions as such or if they are always reported as ext2?
What other techniques should I try? I would very much like to make this work as I get constant low-space warnings in my current setup. Thanks.
Click to expand...
Click to collapse
just used parted to check and it says ext4 .... try using this guide .. worked really well for me to partition my sd ... also if you're having all these problems try wiping dalvik-cache and even data and your ext* partition if it comes down to it
What recovery image are you using?
jndd333 said:
What recovery image are you using?
Click to expand...
Click to collapse
amon ra's 1.2.3
EDIT: lol thought you were the OP
A more careful walk through the partitioning process and I can confirm that everything works as expected, as well as confirming that if upgrade_fs fails, then ext2 is a total dog. One particularly confusing thing was tracking down whether a swap partition was needed or not, but on the latest cyan roms it isn't so I skipped that one.
i repartitioned my sd card with a 64mb swap,2gb ext2 and the rest fat32 using ra recovery. im running cyanogen 4.2.13. when i type 'free' into terminal it says 0 for total,used, and free. am i missing something? or do i need to "activate" the swap partition? TY
here you go
forum.xda-developers.com/showthread.php?t=542899
remember search is your friend
i came across this great site about swapping: http://wiki.cyanogenmod.com/index.php/Compcache
im wondering what other options others on this forum use and which one is the most recommended?
compcache
swap
or
backing swap
ty
backing swap seems to be the way togo, but i would like a professional opinion.
2GB its too much for an EXT partition.....i have seen (somewhere) that the recomended size its 512mb...not sure tought...
About the Swap...idk, but i like Compcache...some devs (like WG) says that their roms runs better without Swap.
EDIT:
Here is what i was talking about the EXT partition.
This was on [Guide] Partition your Sd Card, Upgrade to Ext3, and Install Apps2SD.
nephron said:
Partition Fat32/Ext2 with App2SD
Open up Apps2SD
It will show you a screen telling you that your card is not partition and you will have a sliding bar to choose the amount of space you want for an EXT2 partition
I suggest a max of 600mb for EXT2 space (I use 500mb)
Press Ok
You will get a Force Close screen DONT PRESS FORCE CLOSE PRESS WAIT
You will get a reboot message, Press Reboot
You now have a EXT2 partition
Click to expand...
Click to collapse
is there a specific reason to not have a large ext2 partition? i wanted to have plenty of room for both apps2sd and installing debian. im using this guide:
http://all-google-android.com/googl...verdale's-debian-boot-v-2-0-updated-03092009/
the thing i like about this one:
" this will run a full Linux distribution (Debian) on the Linux partition of your sdcard (EXT2/3/4). I have written the script to bind Debian folders to your regular folders, and thus give you access to the entire system while running Debian"
Firstly, BlaY0 has a great tutorial on how to do this properly, I suggest you do that to learn something.
Secondly, I cannot confirm that this is 100% safe. BlaY0's method should be 99% safe, I don't know about this as it is all automatic. BlaY0's method is tried and tested, this is not. I only used this method as I had a new SD card and I was in a hurry (exams coming up ) and I didn't have time to remind myself of BlaY0's method, and CWM only allows you to create up to 512mb partition. Also, I had a new computer, and I don't have time to set up ADB all over again.
Anyway, this is a method for people who don't want to use ADB to partition their SD card for A2EXT or DATA2EXT (a.k.a. apps2sd, etc etc), and are using Windows. If you're running linux, you could use something like gParted to partition it, not sure about OS X though. This method will allow a Windows user to create an EXT partition on their SD card alongside the FAT partition.
1) Download and install Minitool Partition Wizard, from here.
2) Open the program and delete all partitions from the SD card (which you will have inserted into the computer using an adapter or something). DO NOT DELETE THE PARTITIONS FROM THE HARD DISK! MAKE SURE YOU KNOW WHAT YOU'RE DELETING. Oh, and make sure the SD card is backed up
3) Create a FAT32 primary partition. You decide how big you want it, but I'd advise you leave 1024mb (1gb) for the EXT partition.
4) Create an EXT2/EXT3/EXT4 (you decide) primary partition. Use up the rest of the space on the SD card.
5) Click assign/OK/whatever and wait for it to complete
6) You now have your partitioned SD card ready for an A2SD ROM!
7) You need to assign a drive letter to the FAT32 partition. Not sure about the EXT partition. At first I forgot to do this and my card didn't show up in Windows, though Partition Magic can still see it.
Like I said, do yourself a favour and use BlaY0's method here, but if you're lazy or you don't have time or ADB doesn't work anymore, use this.
Nice one m8. You mentioned that CWM doesn't offer adding partitions bigger than 512 MB. Well, you're right but that's why I made a customized version of fake-flash that can do bigger... to 1 GB. It can even add second ext partition for some exotic types of data2ext. On top of that I added auto block alignment which is described in my guide (the manual one) so no more calculations and manual labour
Sent from my HTC Legend
BlaY0 said:
Nice one m8. You mentioned that CWM doesn't offer adding partitions bigger than 512 MB. Well, you're right but that's why I made a customized version of fake-flash that can do bigger... to 1 GB. It can even add second ext partition for some exotic types of data2ext. On top of that I added auto block alignment which is described in my guide (the manual one) so no more calculations and manual labour
Sent from my HTC Legend
Click to expand...
Click to collapse
Ah, I didn't know about your customized CWM, I think I'll just use that next time
BlaY0 said:
Nice one m8. You mentioned that CWM doesn't offer adding partitions bigger than 512 MB...
Click to expand...
Click to collapse
I remember some version had the ext menu up to 4GB
BlaY0 said:
On top of that I added auto block alignment which is described in my guide (the manual one) so no more calculations and manual labour
Click to expand...
Click to collapse
Didn't know that, good to know, for those of us still using data2ext, this is important...
Wish this was up earlier, spent an hour repartitioning my card using parted.Couldn't upgrade to EXT3 and ended up using CWM 3.0.2.8 to do it instead lol
What CWM is using under the hood for partitioning is actually parted.
Sent from my HTC Legend
Tried it but it didnt work not sure what the problem is...
formatted my SD to FAT 32 and reserved 1G for EXT3 both as primary partition in the Mini Partition Tool
Plugged it in my phone,
Ran ADB shell
# a2sd --enabled, rebooted
on reboot nothing seemed to have changed... went back to ADB shell
tried a2sd --free it says A2Sd is not active ...
a2sd -- enabled again and it says it is enabled but not active
so im guessing it cant read or recognize the EXT3?!
Any clues... i didnt want to move my Dalvik to SD ... should I try EXT4 or even EXT2?
QkSi1ver said:
Tried it but it didnt work not sure what the problem is...
formatted my SD to FAT 32 and reserved 1G for EXT3 both as primary partition in the Mini Partition Tool
Plugged it in my phone,
Ran ADB shell
# a2sd --enabled, rebooted
on reboot nothing seemed to have changed... went back to ADB shell
tried a2sd --free it says A2Sd is not active ...
a2sd -- enabled again and it says it is enabled but not active
so im guessing it cant read or recognize the EXT3?!
Any clues... i didnt want to move my Dalvik to SD ... should I try EXT4 or even EXT2?
Click to expand...
Click to collapse
Take me through what you did, step by step. You say you reserved 1G for EXT3, but did you actually format it as another partition?
QkSi1ver said:
Any clues... i didnt want to move my Dalvik to SD ... should I try EXT4 or even EXT2?
Click to expand...
Click to collapse
It has been mentioned here like a gazilion times, boot up your device with logcat and see the first few lines...there is your answer!
Google how to wait for the device with logcat
1) Downloaded and installed Minitool Partition Wizard from your link. I got the free home edition
2) backed up my SD card and Open the program and delete my SD card partition ( which is in a card reader)
3) Created a FAT32 primary partition of 69xx MB and left the rest 1024 MB for the other unallocated space
4) Right click on the Unallocated Space to create an EXT3 as primary partition with the default cluster size.
5) At this point, it showed 2 partition on my SD, one with the drive letter for windows FAT32, and the 2nd one Ext 3 with 1GB and Primary. Clicked OK and Apply and wait for it to complete.
6) once complete , put it in phone, plugged usb and ran adb shell
7) ran a2sd --enable, it said reboot phone.. i made a mistake to reboot by adb the first time but then did the whole process again a 2nd time using reboot from the phone....
Tried logcat using this command "adb -d logcat>mylogfile.txt"
couldnt find the file anywhere ... if i dont redirect to the txt , it goes too fast to read and there's soo much debug messages what do i need to look for?
I thought it would save me time to get it done through windows... but its taking me as much time it w0uld probably get me with the manual way...
i'll give it a try tomorrow...
8) rebooted fine, and i was still low on space.. so went back in adb sheel to check a2sd --free but this is where it says not active..
QkSi1ver said:
1) Downloaded and installed Minitool Partition Wizard from your link. I got the free home edition
2) backed up my SD card and Open the program and delete my SD card partition ( which is in a card reader)
3) Created a FAT32 primary partition of 69xx MB and left the rest 1024 MB for the other unallocated space
4) Right click on the Unallocated Space to create an EXT3 as primary partition with the default cluster size.
5) At this point, it showed 2 partition on my SD, one with the drive letter for windows FAT32, and the 2nd one Ext 3 with 1GB and Primary. Clicked OK and Apply and wait for it to complete.
6) once complete , put it in phone, plugged usb and ran adb shell
7) ran a2sd --enable, it said reboot phone.. i made a mistake to reboot by adb the first time but then did the whole process again a 2nd time using reboot from the phone....
Tried logcat using this command "adb -d logcat>mylogfile.txt"
couldnt find the file anywhere ... if i dont redirect to the txt , it goes too fast to read and there's soo much debug messages what do i need to look for?
I thought it would save me time to get it done through windows... but its taking me as much time it w0uld probably get me with the manual way...
i'll give it a try tomorrow...
8) rebooted fine, and i was still low on space.. so went back in adb sheel to check a2sd --free but this is where it says not active..
Click to expand...
Click to collapse
Tbh I'm really not sure. One thing I forgot to mention in the guide is that you should assign a drive letter to the FAT32 partition or it won't show up in Windows. I didn't assign one to my EXT4 partition though, and DATA2SD is working great for me. Try deleting all partitions from the SD card and start again. It'll only take 10 minutes, and if it still doesn't work just use the manual way.
Sorry.
alexhtclegend said:
Tbh I'm really not sure. One thing I forgot to mention in the guide is that you should assign a drive letter to the FAT32 partition or it won't show up in Windows. I didn't assign one to my EXT4 partition though, and DATA2SD is working great for me. Try deleting all partitions from the SD card and start again. It'll only take 10 minutes, and if it still doesn't work just use the manual way.
Sorry.
Click to expand...
Click to collapse
Yeah i assigned a drive letter to FAT32...
Also the FAT32 , was my first block allocated partition, the 2nd partition was EXT3... i will redo the whole process and recreate EXT4 instead.
"DATA2SD is working great for me" ... you mean "A2SD working great for me" ... right? unless i'm missing something else that i needed to run..
ps: I recalled, after it was not working, i took out the sd and put it back in the reader to open MiniTool, it showed EXT2 instead of EXT3 ( which i was sure i chose )... and what's weird is it was reporting used space like 41MB... so obvisouly, the ROM wrote something on it...
Formatting it again to EXT3, didnt delete the 41 Used space, but it did convert it back to EXT3 ...probably nothing but mentioning as well
QkSi1ver said:
Yeah i assigned a drive letter to FAT32...
Also the FAT32 , was my first block allocated partition, the 2nd partition was EXT3... i will redo the whole process and recreate EXT4 instead.
"DATA2SD is working great for me" ... you mean "A2SD working great for me" ... right? unless i'm missing something else that i needed to run..
ps: I recalled, after it was not working, i took out the sd and put it back in the reader to open MiniTool, it showed EXT2 instead of EXT3 ( which i was sure i chose )... and what's weird is it was reporting used space like 41MB... so obvisouly, the ROM wrote something on it...
Formatting it again to EXT3, didnt delete the 41 Used space, but it did convert it back to EXT3 ...probably nothing but mentioning as well
Click to expand...
Click to collapse
I suggest you start over, something seems to have gone wrong.
A2SD is where the apps are stored on the EXT partition.
DC2SD is where the dalvik cache is also stored on the EXT partition.
DATA2SD is where the entire /data partition on the phone is stored on the EXT partition of the memory card.
Partitioning the SD card with a FAT32 partition and EXT partition is done first, then you decide which one is for you. DATA2SD does have one or two issues, such as the risk of corruption - you'd then have to completely reinstall the ROM. A2SD and DC2SD are fine but I still found myself running out of internal memory.
i gave up and used ROM Manager to create my partition ...i couldnt set it to 1G because 512MB is maximum but it was painless to create.
it asked me to create a swap partition... i've read somewhere that swap partition is useless or barely used in newer android os? do you guys have any swap partition if so how big are they?
Also, did you move Dalvik cache to sd? isnt it slower on SD? i mean shouldnt dalvik cache be on RAM whihc i assume is faster than any external sd?
thanks for your insight
QkSi1ver said:
i gave up and used ROM Manager to create my partition ...i couldnt set it to 1G because 512MB is maximum but it was painless to create.
it asked me to create a swap partition... i've read somewhere that swap partition is useless or barely used in newer android os? do you guys have any swap partition if so how big are they?
Also, did you move Dalvik cache to sd? isnt it slower on SD? i mean shouldnt dalvik cache be on RAM whihc i assume is faster than any external sd?
thanks for your insight
Click to expand...
Click to collapse
I used the full DATA2SD, which includes Dalvik2SD.
ok so sorry for a double post but im having an issue partitioning.
32 gb card san disk brand new
primary Fat32 10gb
primary Ext2 rest of space
once mini tool is done it sats successful but shows the sd card as Bad disk?!?
is there somthing im doin wrong? is used this guide here http://forum.xda-developers.com/wiki/SD_card_partitioning
all help deeply appriciated
Acer Iconia Tab A110 rooted, Cwm, 4.1.2
Can you actually have a 22gb ext partition? This might be something to look into to see if you can do it.
Edit: this got me interested so I searched myself, yes you can but apparently it depends on the chosen block size and hardware limitations, so u may have an issue with either.
Sent from my Legend using xda app-developers app
alexhtclegend said:
Firstly, BlaY0 has a great tutorial on how to do this properly, I suggest you do that to learn something.
Secondly, I cannot confirm that this is 100% safe. BlaY0's method should be 99% safe, I don't know about this as it is all automatic. BlaY0's method is tried and tested, this is not. I only used this method as I had a new SD card and I was in a hurry (exams coming up ) and I didn't have time to remind myself of BlaY0's method, and CWM only allows you to create up to 512mb partition. Also, I had a new computer, and I don't have time to set up ADB all over again.
Anyway, this is a method for people who don't want to use ADB to partition their SD card for A2EXT or DATA2EXT (a.k.a. apps2sd, etc etc), and are using Windows. If you're running linux, you could use something like gParted to partition it, not sure about OS X though. This method will allow a Windows user to create an EXT partition on their SD card alongside the FAT partition.
1) Download and install Minitool Partition Wizard, from here.
2) Open the program and delete all partitions from the SD card (which you will have inserted into the computer using an adapter or something). DO NOT DELETE THE PARTITIONS FROM THE HARD DISK! MAKE SURE YOU KNOW WHAT YOU'RE DELETING. Oh, and make sure the SD card is backed up
3) Create a FAT32 primary partition. You decide how big you want it, but I'd advise you leave 1024mb (1gb) for the EXT partition.
4) Create an EXT2/EXT3/EXT4 (you decide) primary partition. Use up the rest of the space on the SD card.
5) Click assign/OK/whatever and wait for it to complete
6) You now have your partitioned SD card ready for an A2SD ROM!
7) You need to assign a drive letter to the FAT32 partition. Not sure about the EXT partition. At first I forgot to do this and my card didn't show up in Windows, though Partition Magic can still see it.
Like I said, do yourself a favour and use BlaY0's method here, but if you're lazy or you don't have time or ADB doesn't work anymore, use this.
Click to expand...
Click to collapse
Hahah! Thanks for you detail guide. It is so helpful for me!
CM7 can make you install apps on the sd card, how does it differ from app2sd or app2ext? i have been trying to decide if i should partition my new sd card or its not necessary. There must be an advantage to have app2ext right?
Thank you.
CM7 basically allows you to move all applications using Froyo's app2sd mode. Even ones that have disabled it (like live wallpapers and widgets as those won't work when installed that way).
app2sdext works differently as it will install apps directly to an ext partition on your sdcard (that you manually have to set up). This functionality is NOT build into CyanogenMod, but is easily added with a number of different apps/scripts. This will give you a lot more free space on your phone, and all apps can be installed there regardless of whether they have widgets or have services running. Most app2sdext options will also give you the option of moving the dalvik cache to the sdcard which will save you a substantial amount of space on your internal memory.
Basically, if you want a lot of memory intensive apps, your only decent option with a Nexus One is an app2sdext solution. (I have it with a 1GB partition, and I will soon either need to resize it or delete apps... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
bassmadrigal said:
CM7 basically allows you to move all applications using Froyo's app2sd mode. Even ones that have disabled it (like live wallpapers and widgets as those won't work when installed that way).
app2sdext works differently as it will install apps directly to an ext partition on your sdcard (that you manually have to set up). This functionality is NOT build into CyanogenMod, but is easily added with a number of different apps/scripts. This will give you a lot more free space on your phone, and all apps can be installed there regardless of whether they have widgets or have services running. Most app2sdext options will also give you the option of moving the dalvik cache to the sdcard which will save you a substantial amount of space on your internal memory.
Basically, if you want a lot of memory intensive apps, your only decent option with a Nexus One is an app2sdext solution. (I have it with a 1GB partition, and I will soon either need to resize it or delete apps... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
Click to expand...
Click to collapse
why didnt i think of that? thank you for your reply... now i should decide whether to do it now or wait till i have reached maybe about a hundred apps. by the way does it have any effect on the speed of the phone if you do that?
I am on cm7 and decided to put cache apps on sd card using ta utility is there any other new apps like that? ta
Can you do this with rooted stock?
lolobabes said:
why didnt i think of that? thank you for your reply... now i should decide whether to do it now or wait till i have reached maybe about a hundred apps. by the way does it have any effect on the speed of the phone if you do that?
I am on cm7 and decided to put cache apps on sd card using ta utility is there any other new apps like that? ta
Click to expand...
Click to collapse
I have a class 4 32GB card, and I didn't notice any appreciable difference in speed. I have moved my apps and dalvik cache to the sdcard using DarkTremor's a2sd. I currently have 260 apps installed on my phone, and that is pushing the internal phone space and the 1GB partition I set up for ext. I am about to bug danger-rat for his instructions on how he resized his internal partitions to give the data residing on the phone more space (I will basically shrink the cache partition and I am looking at resizing my ext partition to 1.5GB or 2GB.
I couldn't live without this anymore. I don't know how I went so long without it. It is so nice to just browse the online market and click install on countless apps without worrying about your space.
If you want to try and move the app data (resides in /data/data) to the sdcard, I have heard that it is recommended to have a class 10 card to keep up with speed requirements. I am not sure how many apps support that.
brettbellaire said:
Can you do this with rooted stock?
Click to expand...
Click to collapse
I believe you can. You would have to have a custom recovery. The main thing I am not sure is if it will mount the ext partition. If you have a custom recovery, do a nandroid backup (just in case it doesn't work), flash the zip for DarkTremor, and reboot the phone (the first boot will take longer).
brettbellaire said:
Can you do this with rooted stock?
Click to expand...
Click to collapse
yes you can.
bassmadrigal said:
I have a class 4 32GB card, and I didn't notice any appreciable difference in speed. I have moved my apps and dalvik cache to the sdcard using DarkTremor's a2sd. I currently have 260 apps installed on my phone, and that is pushing the internal phone space and the 1GB partition I set up for ext. I am about to bug danger-rat for his instructions on how he resized his internal partitions to give the data residing on the phone more space (I will basically shrink the cache partition and I am looking at resizing my ext partition to 1.5GB or 2GB.
I couldn't live without this anymore. I don't know how I went so long without it. It is so nice to just browse the online market and click install on countless apps without worrying about your space.
If you want to try and move the app data (resides in /data/data) to the sdcard, I have heard that it is recommended to have a class 10 card to keep up with speed requirements. I am not sure how many apps support that.
I believe you can. You would have to have a custom recovery. The main thing I am not sure is if it will mount the ext partition. If you have a custom recovery, do a nandroid backup (just in case it doesn't work), flash the zip for DarkTremor, and reboot the phone (the first boot will take longer).
Click to expand...
Click to collapse
thanks for the reply i think i read on darktremors post class 4 will do for the data2sd. I have class 4 16GB sd card would 1GB good for the ext? ty
It really depends on how much you think you will be installing. I did a 1GB partition on mine, but now that I install most of the Amazon free daily apps, that space is dwindling quickly. I have programs that will resize the partition for me, but most will have to wipe the card and partition it manually. I do have the install location set to automatic, so it allows developers to specify whether they want it in the "internal" (really it is on the sdext partition, but to the phone it is internal) or external using the froyo method. The Angry Bird apps all default to install on the sdcard, so my installed app base is even larger than 1GB.
bassmadrigal said:
... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
Click to expand...
Click to collapse
I second this
Sent from my Nexus One using XDA App
is it true that cwm sets the partition to ext3 by default? unlike in ra recovery where you still need to convert it? ta
I have heard that it creates it in ext3, but right now, DTa2sd is showing that it is a ext2 partition. I can't figure out how to find out for sure while the card is in the phone. Either way, it is getting mounted as an ext2 partition.
temasek said:
I thought CWM will create ext3 by default? Your steps are ok, np.
Anyway when u read the ext partition type in android, most likely u will see ext2 if u are using official DT script cuz of the auto syntax it uses.
Click to expand...
Click to collapse
then it maybe so, this was posted on the darktremor thread
http://forum.xda-developers.com/showthread.php?p=14134665#post14134665
Well, whether or not it is formatted as an ext3 partition, Android is still mounting mine as an ext2 partition.
Code:
mount | grep ext
NOTE: the "|" is called a pipe. On the keyboard it is the shift option on the backslash key "\". I don't know exactly where it is on the stock keyboard, but on swype it is located under the "D" key when the keyboard has the shift key pressed and you access it by longpressing.
To get your sdcard to ext3, you just need to turn on journaling. You can do this through adb while in the recovery (because you need the partition unmounted to do this).
Code:
adb reboot recovery
adb shell
mount system
e2fsk /dev/block/mmcblk0p2
tune2fs -j /dev/block/mmcblk0p2
reboot
Supposedly Android should auto-mount this as ext3 on boot (which you can check with the first command). At that point, I don't think it will matter what a2sd shows. As the writing of the journal (the big thing with ext3, since it helps minimize write errors on a bad shutdown) is done at the OS level, not the a2sd level.