This message was deleted.

Hi @sparse-monitor-30665 did you ever find a work-around or solution to this? i'm running into the same issue.

The log in the backing image manager is not an error message. Can you check the backing-image-ds pod log instead?

@quaint-alarm-7893, @famous-shampoo-18483 Sorry for the (very long) delay replying. I did not find a work around but I see there is a couple cases open with Harvester and Longhorn related to it. I also no longer have access to those logs as I've now moved on from this setup for now, but I believe those cases sum up what I was experiencing too.

@sparse-monitor-30665 thanks. i'm still having the issues, but we are in the middle of some networking upgrades. i'm going to try it again once we're done with all of that. hopefully early next week. thank you for the ofllow up

@quaint-alarm-7893 I've got 10Gig networking between hosts, and SSD backing storage, so I don't believe it was a network or storage congestion issue, perhaps just a timeout of the other systems as the Windows image is much larger compared to other linux disks that I didn't have an issue with. Of note, I tried it with both a dedicated "Storage Network" for longhorn (in Harvester), and without.

hat's a bummer... i was hoping the network changes would address it! 😕

Hard to say really. I didn't get too far into it but my storage and network appeared to be under utilized. That said, it never hurts to have more bandwidth 😉

agreed 🙂 our networking was a shitshow anyway... so this just gave me an excuse to overhaul it.

🤣👍

msg="SyncingFile: failed to get the checksum from a valid config during processing wrap-up, will directly calculated it then"

This line in

data source pod

means it has already received the file (whole content) it will then try to get checksum from existing config file (if any) if there is no existing config then try to calculate the checksum of it So it is a

info msg

Since the file in the image was large, not sure if it is related to • https://github.com/harvester/harvester/issues/3450 • longhorn fix: https://github.com/longhorn/longhorn/issues/5443 Also we have created an issue for your case https://github.com/longhorn/longhorn/issues/5209