You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was making a 120 gig bagged TAR on Windows with 27703 files and 1432 folders. The bag finished creating, and then there was an approx 7 minute wait before the validation job began. I could see that there was heavy disk usage during those seven minutes. What was happening during this time, and could it be communicated to the user? is it perhaps checksumming the source data? I've already seen a donor wonder about the pause between bagging and validating, where they weren't sure if the job was finished or not.
The text was updated successfully, but these errors were encountered:
I noticed this myself about a week ago, while creating a bag of similar size and file count. I had not seen this behavior before, so I'm wondering if it's the result of some recent changes. I will look into it when I have some time.
I was making a 120 gig bagged TAR on Windows with 27703 files and 1432 folders. The bag finished creating, and then there was an approx 7 minute wait before the validation job began. I could see that there was heavy disk usage during those seven minutes. What was happening during this time, and could it be communicated to the user? is it perhaps checksumming the source data? I've already seen a donor wonder about the pause between bagging and validating, where they weren't sure if the job was finished or not.
The text was updated successfully, but these errors were encountered: