File size mismatch - FOGreplicator

[Sebastian Roth]

@cmachado said in File size mismatch - FOGreplicator:

28268901712 != -1795869360

Negative number?!? This looks like a integer overflow. I’ll take a look at the code when I get home.

[Quazz]

@cmachado Is the OS that FOG is installed on 32 bit perhaps?

[cmachado]

@Quazz Node is 32bit. Server is 64bit.

[Quazz]

@cmachado The integer is overflowing on the node because 32bit has a 2GB limit for integers, but the filesizes exceed that number.

If you get a 64 bit node your problems will disappear I reckon.

[Sebastian Roth]

@cmachado The 32 bit limitation described is probably caused by PHP being 32 bit. I am wondering if there is a way that we can get filesize in KB rather than bytes to get around such issues.

[Quazz]

@Sebastian-Roth https://github.com/jkuchar/BigFileTools possibly.

[cmachado]

This post is deleted!

[cmachado]

@Quazz Yes that worked.

[01-08-20 2:51:25 pm] * All files synced for this item.
[01-08-20 2:51:25 pm] # Windows 10 Class: No need to sync d1p4.img (Link Node)
[01-08-20 2:51:24 pm] # Windows 10 Class: No need to sync d1p3.img (Link Node)
[01-08-20 2:51:24 pm] # Windows 10 Class: No need to sync d1p2.img (Link Node)
[01-08-20 2:51:23 pm] # Windows 10 Class: No need to sync d1p1.img (Link Node)

[Sebastian Roth]

@cmachado said in File size mismatch - FOGreplicator:

Yes that worked.

What exactly worked? Did you reinstall on 64 bit Linux OS?

[cmachado]

@Sebastian-Roth Yes. I marked @Quazz as the correct answer.