This project aims to provide an asynchronous and robust mv implementation, especially for moving directories between local and remote machines with a poor network connection. The syntax is not compatible with mv.

• Asynchronous moving: mvv could execute move tasks concurrently, which opens multiple connections when the source or destination is a mounted net drive.
• Resumable transfer: after the moving process is interrupted (by user, insufficient disk space, unexpectedly closed connection, etc.), mvv continues from the last byte not moved. Although the associated files are still checked byte-by-byte, this is still faster under most conditions.
• Instant removal: source files are instantly removed after being successfully copied to the target location. This prevents the program from using up all the remaining disk space when you only have limited space.
• Progress bar: intuitive interface for viewing progress.

The 3rd point is not equivalent to mv --no-clobber, because in that case mv leaves partially copied files damaged.

cargo build --release
sudo install -Dm755 ./target/release/mvv /usr/local/bin/mvv

There are two main use cases: moving a directory and moving a file.

mvv <source directory> <destination directory> [max number of concurrent tasks]

Please note that destination directory should be exactly where you want to move the files to. For example, mvv ./src/some_directory ./dst/ will move ./src/some_directory/some_file to ./dst/some_file, instead of ./dst/some_directory/some_file. This is an intended behavior in order to avoid ambiguity.

mvv <source file> <destination file> [max number of concurrent tasks]

This usage also follows the rule mentioned above. For example, mvv ./src/some_file ./dst/ will move ./src/some_file to ./dst, instead of ./dst/some_file.

• It's actually cp+rm, so the maximum disk usage could be up to twice the total size. For single files, it's consistent with mv when moving between two filesystems. For directories, the usage is total size plus one single file size, which is smaller than mv.
• Mode bits are not preserved.
• Symlinks are not currently supported.