You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I backup up one app with huge data, I found that my device space use will identifiably go up and I verified the data in /data/migrator/local/$pkgname is not hard-linked to the original data.
At lines 342 and 343, there is one commented "cp -dlR" command and one "rsync -rtl --inplace --no-W". After checking rsync document and this page (See here), I think probably the issue comes from this substitution. Although rsync is much faster than cp, its functions are somehow different.
Possible Solution
I am not quite sure whether the answers given in the StackExchange question are useful. Some more experiments might be necessary. I'm in the tg group, so perhaps we can use tg.
The text was updated successfully, but these errors were encountered:
Description
When I backup up one app with huge data, I found that my device space use will identifiably go up and I verified the data in /data/migrator/local/$pkgname is not hard-linked to the original data.
At lines 342 and 343, there is one commented "cp -dlR" command and one "rsync -rtl --inplace --no-W". After checking rsync document and this page (See here), I think probably the issue comes from this substitution. Although rsync is much faster than cp, its functions are somehow different.
Possible Solution
I am not quite sure whether the answers given in the StackExchange question are useful. Some more experiments might be necessary. I'm in the tg group, so perhaps we can use tg.
The text was updated successfully, but these errors were encountered: