search

SpazeDog / mounts2sd

Android SD-Ext Script+App
GNU General Public License v3.0
76 stars 27 forks source link

Log entry indicates "Not everything from '/data/data' could be moved" #31

Open v173k opened 10 years ago

v173k commented 10 years ago

This is with reference to: https://github.com/SpazeDog/mounts2sd/issues/11

A year latter but maybe I can help add more information to have this fixed for a similar problem.

I am using Mount2SD(v3.48) on T-mobile Galaxy S2 (SGH-T989) with CM10.2. I am getting similar messages:

W/Not everything from '/data/data' could be moved to '/sd-ext/data'
W/Not everything from '/data/user' could be moved to '/sd-ext/user'

Some more information to help debug the problem:

  1. I looked at these directories by booting into recovery (i.e. before Mounts2SD mounts partitions): [x] /data/user as a file called '0' as already mentioned which is just a symlink to /data/data [x] /data/data seems to be populated with data for system apps
  2. If the directories above are emptied (I backed up first though the data seemed mostly redundant only 980 kbytes of files in total and mostly empty directories) Mounts2SD again still gives the same error in the log.
  3. Something seems to be generating the data in the above directories before the Mounts2SD script launches because I seem to have the two directories repopulated again. Its almost as though CM10.2 thinks that it has just been freshly installed and thinks that it needs to populate the data directory for first time boot.
  4. Ofcourse the Warning don't affect normal working of the phone as the mount still completes and Only I want this to be fixed for completeness.
  5. Additional observation. not sure if related: Once booted /sd-ext/data has the symlink '0' !? Even if I delete it, it get regenerated on next boot. Note that this symlink '0' is not in the /data/data directory in the internal memory before boot even in the repopulated /data/data. Not sure how the data is being copied by the Mounts2SD script but I suspect that there is some recursion or link following going on since the symlink '0' points to /data/data

I hope all this is making sense. I can clarify any questions you have or explain further if you like.

Thanks