No shrink from V1.5.5 until V1.6, deploy error, 100%CPU load in node 1.5.2
-
Try the latest init files. You need to manually download those from our server. https://fogproject.org/inits/init_32.xz and https://fogproject.org/inits/init.xz
-
This post is deleted! -
@Quazz said in No shrink from V1.5.5 until V1.6, deploy error, 100%CPU load in node 1.5.2:
Try the latest init files. You need to manually download those from our server. https://fogproject.org/inits/init_32.xz and https://fogproject.org/inits/init.xz
I have downlaod the files, but are the same file in my V1.5.5.
I downloaded the fogproject-dev-branch1.5.5.3 for tests but in V1.5.5.3 is the same error with Zstd.
Now I have the used init files from the V1.5.2 put it into V1.5.5.3.
Now the SSD will be shrink with Partclone/ Zstd in V1.5.5.3.
Is the init file not compatible with my optiplex 9010?
At this weekend I will test image. -
@HG12 There were some changes to how to detect which partitions to resize and which not.
It’s supposed to not mark a single partition disk as fixed size, but it appears that’s not really working as expected, but looking over the code I’m unsure as to why.
edit: Ah, think I may have found the problem.
Why don’t we just test for
if [[ $is_fixed -eq 1 ]]
like on line https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L439This would simplify the code and put the logic on the initial fixed size file creation which makes more sense, imo.
-
@Quazz Not exactly sure how you mean to use
is_fixed
in case of single partition disk?! May I ask you to send a pull request on that so we can elaborate on the code more directly? -
@Sebastian-Roth No, I mean in general, since the logic to extract fixed partitions and handle single partitions is already done in bin/fog.upload which is where the is_fixed variable is based on anyway.
-
@Quazz
Thanks for helping, I will test it next week. Today is end of working day.
I send feedback. -
@Sebastian-Roth https://github.com/FOGProject/fos/pull/24
@HG12 Hopefully new inits will be available then!
-
@HG12 Hey, it’s been a while, is this issue resolved? There are updated inits available (I think) that might have resolved this issue.
-
@Quazz I´m sorry, I was sick for a long time. Now this day is my first day. I will test it if I have time. But I´m busy with an other project. I hope I can test it next week. Please don´t close this thread. Thanks