@Basavarajnc said in FOG 1.5.5 Officially Released:
is there No Effect on Stored Images after upgrading FOG ?
No, there shouldn’t be any effect on the images but make sure you read all the information on upgrading in the link posted by Tom if you have storage nodes!!!
@drak00 said in Fogproject can only clone C disk:
i think if he will use gzip partclone is better than zstd compression
Gzip IS the industry standard for compression. ZStd is the new kid on the block. ZStd was specifically added to FOG because of its tighter packing of the bits in the archive and the faster decompression algorithm than gzip. If you search the forum there were side by side comparisons between gzip and zstd. GZip was left in FOG for compatibility reasons with already captured images. If I remember my discussions with the developers correctly FOG switch over to zstd (zlib) decompressor only because its faster and it can read both zstd and gzipped archives.
@Sebastian-Roth In regards to iperf. When I was bandwidth bench marking some hardware designs, I copied iperf v2 (he’ll have to search for it) to the fog server. Then I pxe booted a target computer in debug mode. From the target FOS system I just uses scp to copy the file to the target computer from the FOG server. This way my testing didn’t impact normal imaging as with the postinit scripts. It gives the same results just without needing to create a postinit script. Its just a different way to go about it neither way is better than the other IMO.
FWIW, I could flood a 1 GbE network link with just 2 simultaneous unicast deployments. That 3rd unicast made the packet error rates jump up quite a bit.
@sgennadi ok the SX6000 IS the the PCIE/NVMe M.2 storage card, gotcha.
I did a quick google search and only found one post where they were talking about getting crc errors in their drive. There is also an ssd toolbox created by adata that can inspect the drive. I’m wondering if there is a firmware update for the drive that might address this error. Lastly since this drive is so new, there may not be a linux driver available yet to properly manage this drive so its using the generic nvme controller driver that is giving you that error.