K2000 package exporting oddity?
Anyone seen "Other" disk space suddenly blow up during k-image export? Here's what I saw today:
During the course of exporting one of my k-images (which once exported is 18.12 GB), the server free space shrank drastically. At one point, "Other" was taking up almost 36 GB (!!!) and I was getting alerts that server space was low.
Thankfully, the exporting finished and soon "other" shrunk back down to around 2 GB, and "exported packages" shows the correct 18.12 GB.
I had always read in documentation that "it is critical that the total size of the exported objects does not exceed the available free space (minus the 20GB of reserve space needed for a healthy K2000)". I never saw reference to temporarily needing about twice the exported image size of working server space! **edited to add: At the start of this export, I had 45 GB free space.
Just wondering if anyone else has seen this behavior before? Thankfully, I'm exporting and deleting to free even *more* space so this will not be an ongoing problem...but it does make me wary of the next export!
Just wondering if anyone else has seen this behavior before? Thankfully, I'm exporting and deleting to free even *more* space so this will not be an ongoing problem...but it does make me wary of the next export!
1 Comment
[ + ] Show comment
Answers (1)
Please log in to answer
Posted by:
agibbons
8 years ago
Not sure this is entirely an answer -- after freeing up a little more space on the server and continuing to export k-images, I stopped seeing this behavior. The working directory/free space no longer blows up to twice the size of the final product for a while. Don't know why...but it stopped happening. I think the K2000 just really, really would prefer to have a ton of free space :)
Exporting files would not have any file DE-duplication or compression involved and could also add to the file size difference when exporting. - TheAustinDave 8 years ago