My file size was very close to 2**31 as well, but I have VOLSIZE=2048 so I figured that 2G was an expected number. Haven't dug in there.
I resolved this problem by deleting the locally corrupted and re-running. I believe what happened next is that it downloaded the full signatures again, and the cloud copy (I store them on S3) was fine. I'm back running again, but the questions still stand:
1. Why is it corrupt? I don't have a crash log handy, but I could try to find it
2. How do I recover? Is it safe to just delete the local files and try again?
3. How can I help improve the system to do a better job of error recovery in this case?
My file size was very close to 2**31 as well, but I have VOLSIZE=2048 so I figured that 2G was an expected number. Haven't dug in there.
I resolved this problem by deleting the locally corrupted and re-running. I believe what happened next is that it downloaded the full signatures again, and the cloud copy (I store them on S3) was fine. I'm back running again, but the questions still stand:
1. Why is it corrupt? I don't have a crash log handy, but I could try to find it
2. How do I recover? Is it safe to just delete the local files and try again?
3. How can I help improve the system to do a better job of error recovery in this case?
Answer to #2 seems to be "delete local copy"