My Venture, with its puny /data internal storage, benefits greatly from using link2sd. However, when I reboot, the dalvik cache is full of real files, not symlinks, and link2sd doesn't automatically re-link the files. I'm not sure if it's wiping and re-creating the dalvik cache or just doing something with those files. It takes a long time to boot and I can repeatedly use df in an ADB shell and watch as /data fills up. Once booted, I have to open link2sd, go to its menu, and choose "Link dalvik-cache files". Not only does this mean that my /data is full after rebooting, but it also means that if I have too many apps to fit in /data then some will end up broken (presumably the ones it attempts to cache after /data is already full). So, my questions are... 1. Is it normal behavior for the system to un-link dalvik cache on boot (either the individual files, or wiping/re-creating the whole thing)? Could this be happening because of some setting I dumbly changed/utility app I monkeyed with? 2. Is it reasonable to expect link2sd to automatically re-link dalvik-cache files on boot? I do have "Relink dex files at boot" enabled. I'm thinking I could chmod the symlinks in /data/dalvik-cache so they're not writable and that might prevent those from being wiped and re-created or whatever, but I don't know if that would break anything (other than having to fix file permissions before uninstalling apps). I guess it couldn't hurt to try on some non-essential apps...could it?