Hello,
I'm not sure if this is a question or a feature request, but I recently tried to rimport a new runoff dataset. Halfway through the first file, I interrupted it with Cntrl-C, and it looks like the file was corrupted in the staging area (about 8GB too small).
If I had permissions for relinking (which thankfully I didn't have) I think the original file would have be overwritten when I ran rimport again.
Is there anyway to have rimport be able to abort the copy operation cleanly? Or maybe have a check with checksums or at least file sizes to ensure consistency before relinking?
Also, Claude had me do sudo -u cesmdata rm to get rid of the corrupted file, which worked (I hope?)
Thanks,
Manish V.
Hello,
I'm not sure if this is a question or a feature request, but I recently tried to rimport a new runoff dataset. Halfway through the first file, I interrupted it with Cntrl-C, and it looks like the file was corrupted in the staging area (about 8GB too small).
If I had permissions for relinking (which thankfully I didn't have) I think the original file would have be overwritten when I ran rimport again.
Is there anyway to have rimport be able to abort the copy operation cleanly? Or maybe have a check with checksums or at least file sizes to ensure consistency before relinking?
Also, Claude had me do
sudo -u cesmdata rmto get rid of the corrupted file, which worked (I hope?)Thanks,
Manish V.