Database Develop

[Q] Possibly quick noob question? Help needed! :)

Right now I'm using CM 6.1.1 on my Nexus One. When I flashed CM for the first time I wiped my SD card right after I installed the ROM, so I really don't remember too much about what happened to my apps or anything like that. So, my question is, if I want to install CM 7, can I just wipe my phone with ROM manager right before installing it, and then not wipe my SD card afterwards? Will the apps, pictures, ect., that is on my SD card right now magically appear untouched on CM 7? I guess I'm just not sure how the SD card contents will be affected when flashing ROMs, and I'm not sure if after you flash a new ROM, the ROM can use all of the stuff that's on your SD card just like the ROM you had before did.. Does that kinda make sense? I feel dumb for asking all this. Also, when I save a backup of my ROM, the backup will just be a copy of all of my phone's internal memory and the operating system, right? And when I wipe my phone and install a new ROM, the new ROM just replaces all of my phone's old contents? So if I ever flashed my original ROM again, it'd bring back all of my phone's contents, system memory, operating system, apps installed on the phone, ect?
Thanks for taking the time to read my long, poorly written batch of questions Help would be very very appreciated!

SD card isn't touched when flashing ROMs.
You can restore your backup and it'll be all like it was.
If you use DT A2SD - things start being more complicated.

Yumunum said:
can I just wipe my phone with ROM manager right before installing it, and then not wipe my SD card afterwards?
Click to expand...
Click to collapse
Yes, you can leave your SD contents as is, they won't be touched.
Will the apps, pictures, ect., that is on my SD card right now magically appear untouched on CM 7?
Click to expand...
Click to collapse
Pictures, Music, Videos etc that are stored on the SD card will remain untouched by flashing a new ROM, however apps are a different story. Basically you've got two main types of Apps on SD cards. The first is froyos implementation which is basically used to free up space on the phone memory but will not survive a wipe or flashing a new ROM. The alternative is Dark Tremors A2SD which uses a dedicated partition on your SD card (Created through recovery) to store apps by tricking the system into thinking the folder on your SD card is actually on internal memory. Once a new ROM is installed over the current (Which obviously must use DT A2SD also) these apps should be available again with their settings etc remaining.
I guess I'm just not sure how the SD card contents will be affected when flashing ROMs, and I'm not sure if after you flash a new ROM, the ROM can use all of the stuff that's on your SD card just like the ROM you had before did
Click to expand...
Click to collapse
Again, all data/media remains but apps require A2SD or its variants.
Also, when I save a backup of my ROM, the backup will just be a copy of all of my phone's internal memory and the operating system, right?
Click to expand...
Click to collapse
When you backup/nandroid you take a screenshot of sorts of your system. By default I think most recovery images save the boot, system, data and cache partitions when a backup is being made. Certain recoveries offer to backup other partitions such as sd-ext (Where A2SD stores the apps). Backups are designated by folders with a time stamp, I personally rename these to reflect the contents e.g. MM.v.20 tells me this is MicroMods v.20 of his GB ROM. Obviously yours will differ but I find this keeps things organised. Basically think of nandroid as the Android equivalent of Acronis true image or Norton Ghost for the PC. It lets you create any number of backups which will restore your device to the exact state at the moment of backup.
And when I wipe my phone and install a new ROM, the new ROM just replaces all of my phone's old contents?
Click to expand...
Click to collapse
A newly flashed ROM will basically restore your device to factory settings but on the new ROM. Once you've signed in to your Google account certain settings and content will be automatically downloaded e.g. Calendar appointments, Contacts. Other settings will not be restored e.g. Display brightness, alarms.
So if I ever flashed my original ROM again, it'd bring back all of my phone's contents, system memory, operating system, apps installed on the phone, ect?
Click to expand...
Click to collapse
Nope, again it would return to the factory settings. However you can restore nandroid backups you have made of your original ROM which would return the system exactly to its previous state.
Basically if you're on a stock ROM it won't have A2SD. If you wish to use A2SD from now on then find a ROM which uses it, partition your SD card appropriately (Plenty of guides around) and you'll have minimal problems moving from ROM to ROM. As for Nandroid you'll find that most ROM devs recommend wiping all data from the phone (Not SD card) before flashing their ROM. Otherwise files or settings from other ROMs can cause some undesired effects on your current one.
Good luck and get reading the Nexus wiki, it's very helpful for these types of questions
Note: For some reason I vaguely remember someone noting that Froyos A2SD can be used to move apps to another ROM or at least the base app itself (If not the individual setup/settings) but I can't seem to find any info after a quick Google and it never interested me enough to look into it further. Perhaps someone can clear this up?

Hollow.Droid said:
Note: For some reason I vaguely remember someone noting that Froyos A2SD can be used to move apps to another ROM or at least the base app itself (If not the individual setup/settings)
Click to expand...
Click to collapse
I dont think thats true.. suppose it's formatted during a wipe.. titanium backup serves the purpose like a charm.. (with all the settings for the apps and the resumes for the games)
Sent from my Nexus One

I have a similar question to the OP. I use a 1GB EXT through DT's A2SD. If I wanted to flash a new ROM would the following be my step-checklist?
1 - Nand backup (just in case)
2 - Backup apps with Titanium
3 - wipe system data & cache
4 - flash new rom
5 - restore apps?
I'm just wondering what the procedure is to keep the apps in A2SD on a new flash without re-setting up.

Wiggz said:
I have a similar question to the OP. I use a 1GB EXT through DT's A2SD. If I wanted to flash a new ROM would the following be my step-checklist?
1 - Nand backup (just in case)
2 - Backup apps with Titanium
3 - wipe system data & cache
4 - flash new rom
5 - restore apps?
I'm just wondering what the procedure is to keep the apps in A2SD on a new flash without re-setting up.
Click to expand...
Click to collapse
yeah that would be fine..
btw 1: if you upgrading a cm nightly, you need not wipe system n cache..
2: if you do a titanium backup before, then you can finish all the steps in the recovery in one go..
n I dint quite get what you are asking. but from what I know, apps 2 sd folder (ie android.secure) is erased in a wipe.. that isnt changing
Sent from my Nexus One

shreyas - thanks for your help.
I understand the A2SD (EXT) partition onthe sd will be wiped, but I'm assuming I would have to do nothing to get the new rom to see the ext and use it?
That's really my question. Would recovering my apps from Titanium push them back on the A2SD location or would I need to install A2SD again?

i don't think so..
I suppose that the pro version must support the direct a2sd.. but give it a try.. if it dosent work then you have do manually..
Sent from my Nexus One

[Q] [Request] Need a way to boot 2nd partition (SDext) during boot time

Hi there,
So my N1 is rooted and has SuperOSR rom installed. The native app2sd that comes with the rom failed to work, so I disabled it and went back to the method I was using on CM7, Link2sd. I need a method to move apps/cache/lib files to sd-ext, as the tiny internal storage on the N1 is insufficient to hold even a 10th of the apps (and their data) that I have installed. And Link2sd has, at least in the past, been the perfect option to do so.
At first, all seemed well after installing and setting up Link2sd. Mount scripts were created with no problems, apps/cache/lib files all moved over to sd-ext without a hitch. Everything was going really well. Until I rebooted. Then, all hell broke loose.
The problem is this - for some reason, the second partition (sd-ext) is not being mounted during boot time. I'm not sure why, as this is exactly what the Link2sd mount scripts are supposed to accomplish. A Link2sd "mount warning" notice confirmed this problem, saying that "since 2nd partition was not mounted during boot time, linked apps will be invisible to the system until quick reboot". Indeed, every app that I had linked was not visible to the system, and most widgets on my homescreen showed only the message "problem displaying widget".
Luckily, a way to temporarily fix this is by simply quick-rebooting the rom. This will get the linked apps to show up again. But the problem is, widgets are still dead, input method gets reset (goes back from Swiftkey to native Android keyboard), and SMS gets reset back to the standard android SMS app. Of course, all of this can be changed back, but it takes time and effort to load each individual widget and restore each individual input/sms setting. It's really not practical every time you have to reboot your phone that you have to:
1. Quick-reboot the rom
2. Change input method back to Swiftkey
3. Manually restore every widget on your home screens
4. Change sms app back to Go sms.
So, my question is, how do I avoid having to do all this? I've already tried the "re-create mount scripts" option on Link2sd, but it doesn't matter. Still have the same errors upon rebooting phone every time. I'm pretty sure this means that the Link2sd mount scripts are either not being created correctly, or are being deleted every time the phone reboots. How do I fix this? Trying to get in contact with the developer of the app (bakpinar) has proven unsuccessful.
Does anyone know of any other scripts that I can flash/install that will successfully and consistently mount the 2nd partition (sd-ext) during boot time? I'm fairly certain that this is all I need, as everything else with Link2sd has been working correctly. Thanks in advance for any advice!

Ok, so since I haven't gotten any responses on this, I'm going to attempt two methods that i THINK might remedy this issue. The first one is this:
Method 1:
1. Full wipe and reinstall of SuperOSR rom
2. Format sd-ext to ext3 filesystem (found out that rom's native app2sd program wouldn't work due to my sd-ext partition being FAT32)
3. Enable rom's native apps2sd option upon booting.
4. Reboot
5. Install Link2sd from market, enable dex/lib file linking ONLY (native apps2sd program only moves app files, not dex or lib). Going to be interesting to see what link2sd says about the mounting scripts...
6. Reboot, collect results.
The 2nd method I'm going to try is this.
1. Full wipe and reinstall of SuperOSR rom.
2. Flash DTAPPS
3. Boot into ROM
4. Download and install test applications
5. Collect results
I'm not sure if either of these methods will work, however I know the 2nd method worked for CM. I will update a bit later as to which method (if any) fixed the issue. Sorry for the double post.

I commented to the ROM cook nelo360 a while back that there are some strange sd-ext mounting issues. If you look at the dmesg as it boots, it does post some strange error messages. Essentially, ext3 mounts as ext2, and ext4 mounts as ext3. Despite it not mounting as the proper format type, it still works.
Since the ROM is pulled off of AOSP, as CM is too, sort of, much of the same apps2sd apps probably work decently well.
Definitely need an ext3 or ext4 partition. As I'm understanding your post, that did not happen initially, and is crucial to many apps2ext to work, including the built-in one.

Really? Ext4 as 3 and ext3 as 2? Well that would explain why Link2sd was having issues. Hmm.
What I ended up doing was fully wiping the phone, flashing the rom, and then immediately afterwards flashing DTAPPS. Using the GUI interface found on the market, I moved apps to sd-ext and cache to sd-ext as well. The result has been mixed. While there was noticeably more space initially to install apps (something like 190mb internal), that space has declined at almost as fast a rate as when I had no apps2ext of any sort installed at all. This makes me think that while DTAPPS successfully moved some of the initially installed apps over to the sd-ext, it hasn't been moving any new ones i've installed or their cache files. I tried re-moving apps/cache with the gui interface and by using the old-fashioned terminal emulator method, but had no success. Still looking at about 100mb free space on internal. Considering that I only have about 1/4 of the apps installed that I usually have installed on my phone at any given time (I use A LOT of apps), it's become apparent that soon I am going to run out of space again.
As I can't find any method to fix this, I'm afraid I'm going to have to call it quits with this ROM and try something else. Which is a real shame, because stability-wise this ROM beats Cyanogenmod and other ROMS I've tried hands down, while not sacrificing many features. I guess for a user who doesn't use a lot of apps or need a lot of space for them, this ROM would be ideal. Unfortunately, I'm not that type of user.

One problem I've found is that with any automatic apps2sd/ext system is the control of what is actually on the SD vs. internal memory is hard to work out.
With the built in apps2sd, which you seem to have trouble with, not every app was transferred to ext. I found that with the built in system, my internal memory kept dropping until it hit 25 mb or so. However, it never really dropped below that. Everything I kept installing probably went to the ext partition. I installed a lot of apps, and it wasn't an issue. (But you're right, it may not be as many as you want).
I didn't have a great way to check this though. Root explorer showed both the data/apps/ folder and the sdcard/ext folder linked together, so it just listed everything together. I'd have loved a way to actually manually transfer whatever apps were on internal memory to ext, but never found an easy way to do so, or even to confirm what was in which directory.
So even though it looks like the internal memory is steadily and quickly dropping, if you continue to install, and have the two directories appropriately linked (sorry, I don't know what the difference between all the different kinds of scripting apps2sd are), I don't think you'll run out of space as quickly as you think you will.

[SOLVED] SD-EXT doesn't mount on boot

Hi,
If you experienced this problem go to the 6th post where the answer is.
Have a weird problem.
SD-EXT partition seems to not mount and be discovered by system at boot. As a result cannot use DT, S2E for CM7.
Here is some background info, I suppose my diagnosis is right. Please help
I bought google-branded Nexus One with Eclair, opened the bootloader installed CWM, partitioned SD card and installe newest CM7 nightly with gapps and DT. That made the phone reboot each time any new app was installed.
I tried with different DT versions, S2E app from Market and the problem wasn't solved. Then tried MIUI, but when enabled A2SD there all apps from data were gone.

The card might need to be repartitioned/reformatted.

Did that as well, even have used different cards, formatted on different recoveries and so on. Now I found out method of Data2SD from Desire, it works on CM7 and MIUI, but I am afraid of poor performance as dalvik and data of apps are on SD-EXT now...

You could try to perform a simple copy test to/from /data and to/from SD-EXT, to know how do the speeds differ, if at all. Internal memory of Nexus isn't really speedy.

You mean via ADB? I'll send some file as soon as I'll be on Win and give it a try
After all I noticed that both SD cards were Class 2, whereas in my Wildfire I have class 10. But that really shouldn't make that difference, should it?
Also an app Link2SD works fine, so the partition itself is accessible.
I also noticed, that on Wildfire there are 4 statbars in menu (Internal Memory, System, SD card, sd-ext), but on Nexus the last one is gone. This is why I think something curious is about mounting.
Does anyone know at what stage of boot DT A2SD is activated? When the SD-EXT partition gets mounted?

Nexus One controller speed is limited, so anything beyond Class 4 most probably will be simply a waste.
The SD-EXT should be mounted when the kernel is up and running the boot scripts (/system/init.d/*). Usually it's mounted in one of the first scripts (they're numbered, and run by number sorting order).
The tab in the phone menu is an option of specific ROM. No stock ROM supports A2SD, so in order to get this tab you need a custom ROM that has this specific option integrated. I don't know of any - though MIUI most probably has it.

[SOLVED]
Thx all for help.
It was radio to blame. I installed CM7 after stock Eclair with very old radio.
Solution: go back to stock Eclair, do all OTAs and try once more with A2SD.
(and never buy a Wildfire to be afraid of doing OTAs on Nexus (I've lost root possibility by doing OTA on WF))

[q] help! Can't clear phone data

Ok, long story short, I have 113MB of 'system data' in my /datadata folder (66% full), and I want it gone.
But I can't get rid of it... I've tried a full clean install, I've tried manually formatting /datadata from CWM, and I've also tried formatting boot, cache, data, datadata, and system from CWM followed by a fresh install (Kang 12/17).
My wife has the same phone and ROM and she only has 26% full in /datadata. I can't - for the life of me - figure out how to completely clean /datadata.
One thing I noticed in terminal emulator is that the data in /data and /datadata is about equal to what is listed in /system. However, formatting /system did not clear it out.
Please help as this is driving me insane!

Isn't datadata based on your apps? Like dalvik? I think ur wife just has less apps.

mbc663 said:
Isn't datadata based on your apps? Like dalvik? I think ur wife just has less apps.
Click to expand...
Click to collapse
I thought so to, but even with no apps (nothing but what comes with the ROM) I have 3x what she has... and she has what comes with the ROM plus all her other apps.
If it does have to do exclusively with the apps, I'm more than willing to do everything step by step to figure out which app(s) cause my issue, but in order to do that I need to be able to clear the folder of everything except what true system data is necessary and start from square 1.

/datadata is apps settings and data. A little more info might help...

b-eock said:
/datadata is apps settings and data. A little more info might help...
Click to expand...
Click to collapse
What kind of info do you need, and I'll try and supply it. I'm trying to do a clean install so that all of those app settings and data are starting from scratch. Factory resets didn't do it, formatting the folders through CWM didn't do it...
I must be missing something... but I can't figure out what it is.
Some basic background:
Most recently on the 12/17 Kang (CM7.2 RC0) with the glitch v13 (2.6.35.13) kernel and Gapps 08/28
For the just completed testing I only flashed Gapps (08/28) and the 12/17 Kang so I could see if anything I did worked on clearing /datadata.
Other than that, the only modification I've done to my phone is the modem is KG3 i9000.

Have u tried Titanium Backup Pro app ??

4-2ndtwin said:
Have u tried Titanium Backup Pro app ??
Click to expand...
Click to collapse
I haven't... I have the free version currently. Would the pro version do all of this stuff?

The free version should do for deleting data and removing apps.
Sent by XDA Premium App

I'll go out out on a limb here but try backing up your sd card and formatting it?

mbc663 said:
I'll go out out on a limb here but try backing up your sd card and formatting it?
Click to expand...
Click to collapse
I had thought of that too... once formatted and I reinstall the ROM and stuff, is it easy enough to just copy those folders back on the phone? That was the one thing I was worried about... and thus I hadn't tried yet.
Formatting always makes me nervous

Are you encountering any issues with it being that full? Or is this just to satisfy your ocd?

theyurtingyeti said:
I had thought of that too... once formatted and I reinstall the ROM and stuff, is it easy enough to just copy those folders back on the phone? That was the one thing I was worried about... and thus I hadn't tried yet.
Formatting always makes me nervous
Click to expand...
Click to collapse
As simple as dragging and dropping files. Also nice to start fresh every once in a while to clear out junk from old apps.

I'm getting ready to format my SDcard and start all over... but if I format my SD card, I'll no longer have my ROM zips there to flash. I put the ROMs on my external SD card (emmc), but in CWM I can't mount emmc to make sure they are there to flash when I format my SDCard...
How do I get my ROM flashed again once I format my SD card?
EDIT:
Doing more research it appears that I should be able to format my SD card w/o losing my ROM as long as I leave my boot and system folders alone.
So, if I format /data, /datadata, and /sdcard I should be able to reboot and see if it worked

studacris said:
Are you encountering any issues with it being that full? Or is this just to satisfy your ocd?
Click to expand...
Click to collapse
I am encountering issues with it being that full. I have like 70 apps with approx 38MB of data taken up... combined with the large amount of 'system data' in the /datadata partition I'm running into the issues when that folder gets to 90% capacity.
It's at the point that I can't install new apps that save any data at all or I will have to constantly shuffle which apps can save their data. Doing research I found that the 172MB cap shouldn't be an issue unless you are hording apps... I have a small number of apps with a small amount of data, so things should be better

Thanks for all the suggestions...
But so far nothing has worked.
I formatted the SD card along with data and datadata and rebooted the phone.
My /datadata folder was still listed at 66% full. So formatting nearly everything still couldn't clear this folder.
I'm still boggled why the other captivate started with 8MB system data and I start with 113MB, both on a clean install...
Perhaps my only hope is to clear stuff out again and flash ICS and hope that something is different enough that this 'problem' goes away...

An additional thought
Would I be able to delete the /datadata folder through Root Explorer, reboot into recovery and reflash the ROM?
I would assume the ROM will repartition the phone correctly. System data can't exist in a folder that doesn't exist - right?

Galaxy S-NAND chip, datadata partition, JB and ICS queries

So quite a comprehensive list of stuff in the title but I believe this will help many people including myself. I've browsed through various ICS and JB threads and picked up bits and pieces regarding to my questions but I'd like to know more, so if developers or people could help me out it would be much appreciated.
First, I've read that the SGS has pretty bad NAND disk (at least compared to today's standards), and thus suffers from lag due to bad I/O performance, something which the CPU or RAM could not compensate for. I've bought my unit in early July 2010 so I don't see it any better than the many units that were produced later, seeing as my device is one of the very first batches produced. Is it true that the lag is coming from the NAND disk, and not the comparatively slow CPU and low amount of RAM, and that software can only do limited work to alleviate this problem?
Second, I'm confused about the entire existence of /datadata partition. This was non existent during the gingerbread days and was the "culprit" of the low memory notifications found in early ICS builds like teamhacksung and icssgs, but I understand it as "a fast partition that allows for faster data access compared to the /data partition, which is slow'. So is the /data partition entirely hopeless compared to /datadata?
How does /datadata work in the first place? Since it wasn't there (or was it?) during Gingerbread days, was it magically created with some witchcraft? And why are JB Roms being created without /datadata (other than no having enough system space)? Is it fast enough without the partition already?
I'm sorry for all these questions but I'm just so curious Many thanks in advance.

Not sure what Samsung originally used the /datadata partition for.
I don't think JB developers have decided whether to use /data or /datadata. I think it depends on if project butter makes /data fast enough. Elite has recently changed his latest beta rom from /data to /datadata so we'll see.
Using the small /datadata partition shouldn't be a problem if you install datafix from the Play Store. It moves all the big non-performance critical files (lib) to /data leaving the rest on /datadata, so you get the best of both worlds. You can also move selected apps and cache to /data too.

The butter project has nothing to do with the nand. vsync and tripple buffer is only for rendering
the benchmark of the onenand and the movinand like read/write and iops would be usefull to determain if the datadata partition on the onenand is necesary.
therefore the different posted benchmarks. at least thats what i got form it
is there a easy way to test the different nand chips on the phone more specific?
like hdtune test?
so the iops can be tested also with different sizes?

Vertron said:
Not sure what Samsung originally used the /datadata partition for.
I don't think JB developers have decided whether to use /data or /datadata. I think it depends on if project butter makes /data fast enough. Elite has recently changed his latest beta rom from /data to /datadata so we'll see.
Using the small /datadata partition shouldn't be a problem if you install datafix from the Play Store. It moves all the big non-performance critical files (lib) to /data leaving the rest on /datadata, so you get the best of both worlds. You can also move selected apps and cache to /data too.
Click to expand...
Click to collapse
I have indeed tried to use datafix but for some reason I get android.process.media stopped working every time I tried to use it (both in ICS and JB). Installing data scripts (like the one called SDatafix.zip) from the Development forum does help me solve the low storage problem but I do no gain control of what apps I want over at /datadata. Not sure if those data scripts are compatible with JB, so I'll stick with ICS for now.
Now that I think about it, performance does seem to be affected by disk speeds, not just in phones. My dual core i7 (nehalem, arrandale) notebook fitted with a 2nd gen SSD can open up chrome quicker than my quad core i7 (sandy bridge) all-in-one with a 7200rpm disk, and performance is consistent even with multiple applications open, while the 7200 rpm struggles to keep pace despite the superior processor (and same RAM). Guess the lag is really coming from the disk, or is it?

hey can i restore nandroid backup of one ROM to its higher release..???? like i backup REM-ICS V1.2 so can i restore it n REM-ICS V1.3..???

You shouldn't have any issues using the datafix app with ICS.
What I normally do is; install a stock gingerbread rom, followed by the ICS rom. Install the datafix app then install the script & reboot, recover everything from titanium backup, reboot again. Open the datafix app select everything I want on /data then install & reboot again. I don't have any force close issues by doing this.

Vertron said:
You shouldn't have any issues using the datafix app with ICS.
What I normally do is; install a stock gingerbread rom, followed by the ICS rom. Install the datafix app then install the script & reboot, recover everything from titanium backup, reboot again. Open the datafix app select everything I want on /data then install & reboot again. I don't have any force close issues by doing this.
Click to expand...
Click to collapse
Hmm, here's how I did my fix. I did a 3 wipe (data, cache, dalvik cache) and restored all my stuff via TB first, when the low notification icon comes up, I reboot my phone then go into datafix to clear out some stuff to /data and continue the restoring process until its finished. Its alright for the first couple of minutes but then that media thing keeps FC ing.
How are you supposed to choose what apps you want under /datadata or /data when you haven't restored them yet? Or is datafix somewhat integrated with TB and reads your TB backups in the SD card instead of the ROM so you can select what apps you want to move to data and so on? (in fact I'll try that right now after a nandroid backup).

ballsofsteel said:
Hmm, here's how I did my fix. I did a 3 wipe (data, cache, dalvik cache) and restored all my stuff via TB first, when the low notification icon comes up, I reboot my phone then go into datafix to clear out some stuff to /data and continue the restoring process until its finished. Its alright for the first couple of minutes but then that media thing keeps FC ing.
How are you supposed to choose what apps you want under /datadata or /data when you haven't restored them yet? Or is datafix somewhat integrated with TB and reads your TB backups in the SD card instead of the ROM so you can select what apps you want to move to data and so on? (in fact I'll try that right now after a nandroid backup).
Click to expand...
Click to collapse
I think you are getting force closes because your /datadata partition is too full before you run the script. TB works fine with the datafix, as long as you enable follow symbolic link in the preferences.
Another thing I should mention is it's probably a good idea to not recover everything from TB at once. Do it in 2 or 3 batches, restarting after each one, that way /datadata should never get too full.