Imaging runs take up a lot of space. When the hard drive fills up, current method is:
Perform google drive upload
Delete folder manually with rm -rf images/*
Continue
But it's VERY error-prone. Here are some ideas I have (along with upgrading to a larger hard drive)
Use rclone move instead of rclone copy. rclone move performs an upload and then deletes the local file after verifying the hash of the uploaded file matches the local file.
We check if hard drive is at 90% capacity before starting an imaging run, and if so, we alert the user and tell them to perform an rclone move before continuing
We do what dashcams do: Delete the oldest imaging run to make space (after ensuring it's been uploaded). Problem is, the size of each run is not necessarily fixed (images vary in size, and number of images may vary (top-only or full run)), so it's hard to know how much we need to delete to be "done".
Imaging runs take up a lot of space. When the hard drive fills up, current method is:
rm -rf images/*
But it's VERY error-prone. Here are some ideas I have (along with upgrading to a larger hard drive)
rclone move
instead ofrclone copy
.rclone move
performs an upload and then deletes the local file after verifying the hash of the uploaded file matches the local file.rclone move
before continuing