The current check for max chunk size being within required bounds of 1MB to 1GB occurs after converting the max chunk size from the user to bytes from mb. This can cause an overflow without a proper error message if the user tries to input the max chunk size in bytes and ends up well beyond the limit of the command. We should check the bounds without the possibility of overflowing the int if the user input an invalid value.