Image Size
-
1.14
2.Single Disk Re sizable
3. 1.4.4 -
What’s the “manager”? 9 is maximum for Partclone GZip, and it likely reset to compression 6 during capture. 10-19 is good for the ZStd compression type.
-
I did one as Parclone Gzip and one as Partimage both came out to roughly the same size of the data on the HDD I will try taking a partclonezstd image.
-
@Jarl2.0 What is the total size of data (not hard disk size) on reference image as viewed by MS Windows?
-
47.3GB which came out to a roughly 46.3 GB image
-
@Jarl2.0 I just want to be clear on this, when viewing the total disk size in Windows its 47GB in size? And when you look at the image file size from the linux server point of view on the fog server the captured file size is 45-55GB?
-
Yes the machine that came in at 47GB in Windows had a 46GB image file on the server. I’m taking a new image using partclonezstd now to see what that one comes in at.
-
@Jarl2.0 said in Image Size:
46GB image file on the server
OK we will wait.
But I’m still unclear how you derived this 46GiB number, actually I suspect this number isn’t accurate for its true file size on the fog server. Is that from the web gui or actually looking in the linux OS on the server?
-
This image came out to 17gig on the storage node which is great I’ll will keep tinkering with it to find a good compression ratio that also has a good deploy speed.
Thanks!
-
@Jarl2.0 If you are using zStd capture speed will be much slower than deploy speed. That is the nature of the compression tool. With gzip you don’t get as good of compression ratio or deploy speeds, but capture and deploy are similar in speed. For Zstd 11-13 is probably a pretty good range to stay in.
