Replies: 4 comments 13 replies
-
|
No, shrink-backup will not recalculate due to other mounts or excluded paths in exclude.txt. https://github.com/UnconnectedBedna/shrink-backup?tab=readme-ov-file#info
In this situation where you want the img smaller than files on root, and not just "make sure all data fits", try running shrink-backup with shrink-backup does not calculate space on all data to be backed up, it simply performs a general check of how much minimum space is needed for all files on root to fit to make sure the backup does not fail due to out of space. But if the backup img file becomes 18G but only data on let's say 10G of those, compressing the img with external tool will probably make the 8G "empty space" take up a few bytes, since all the "data" in those 8G will be zeroes.
Mounted partitions will never be included in the calculations, but that is the other way around, ie it is NOT included in the size calculations even if not excluded in exclude.txt. This could potentially be "fixed" with a new option where shrink-backup is running a full
Moving Let me know if I can clarify closer. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Thank you for your detailed answer. |
Beta Was this translation helpful? Give feedback.
-
|
Try running pishrink on the image, that would be the easiest solution if it works. (might be introuble for missing boot partition, idk) I'm going to take a hard think if maybe implementing an option, like Edit |
Beta Was this translation helpful? Give feedback.
-
|
There you go: 0f39c81 Try running script on testing branch with |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
No wait, that's not going to work, it still makes the calculations on the root partition, I need to make a few changes... |
Beta Was this translation helpful? Give feedback.
-
|
I won't be able to test until tomorrow so take your time! :-) |
Beta Was this translation helpful? Give feedback.
-
|
There, I think this should work. No better way than to test on a live victim. xD Let me know. :) |
Beta Was this translation helpful? Give feedback.
-
|
Didn't work. Looks like there might be an error around line 2810? Log: |
Beta Was this translation helpful? Give feedback.
1 reply
-
IMG_SIZE is empty. If update=true... But the new calculated size is 3.35G ( I implemented a simple check if the variable is empty and running a stat on the img if it is. Please update and try again. :) |
Beta Was this translation helpful? Give feedback.
-
|
SUCCESS! Well done! Log: |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
Ok, I don't use -U, but good to know. Seems to me we had this issue before, the fix was to restart the computer, IIRC, but I don't know that a solution was found? |
Beta Was this translation helpful? Give feedback.
-
yeah, if that was the sollution before, do it again, because none of the code changed is even ran at that point. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, we and the other user weren't able to get to the bottom of what the issue was. |
Beta Was this translation helpful? Give feedback.
-
|
Log: |
Beta Was this translation helpful? Give feedback.
-
|
Right, it's that thing. I have in detail described what is needed in that thread you linked to if you want help with that, because I have never been able to reproduce that on any installation. The exact line ran according to your log was: I have no idea why your system suddenly have mmcblk0 and mmcblk1. This is basic linux stuff so you have to figure that one out on your side. The script did not change, your system did. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The size of the files once exclude.txt is factored into it is about 2.22GB. You can see in the log where the debug Rsync reports the size of the files copied. However, shrink-backup is making an 18GB image file.
All I can imagine is that it's not excluding the
/imagesfolder in it's calcuation, which would make up that difference. It IS, however, NOT including the/media/usbfolder, which over 60GB, but is also in the exclude.txt, but that's also where the image file will be written, so it's excluded by default I expect.log file:
Beta Was this translation helpful? Give feedback.
All reactions