Possibly no safety check when staged file is corrupted with Cntrl-C Interrupt

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.

Start with the rimport copy and relinking flow described in the report, and reproduce an interrupted copy with Cntrl-C. Determine how the staging file is handled before relinking; done should mean an interrupted or inconsistent copy cannot overwrite the original, with the chosen consistency check covered by tests.

Scritto dal modello di indicizzazione a partire dal testo della issue.