Nick Craig-Wood 4e9b63e141 azureblob: cleanup uncommitted blocks on upload errors ...

Before this change, if a multipart upload was aborted, then rclone
would leave uncommitted blocks lying around. Azure has a limit of
100,000 uncommitted blocks per storage account, so when you then try
to upload other stuff into that account, or simply the same file
again, you can run into this limit. This causes errors like the
following:

BlockCountExceedsLimit: The uncommitted block count cannot exceed the
maximum limit of 100,000 blocks.

This change removes the uncommitted blocks if a multipart upload is
aborted or fails.

If there was an existing destination file, it takes care not to
overwrite it by recomitting already comitted blocks.

This means that the scheme for allocating block IDs had to change to
make them different for each block and each upload.

Fixes #5583

2025-01-22 11:56:05 +00:00

..

azureblob_internal_test.go

azureblob: cleanup uncommitted blocks on upload errors

2025-01-22 11:56:05 +00:00

azureblob_test.go

build: remove build constraint syntax for go 1.16 and older

2024-04-18 16:53:55 +02:00

azureblob_unsupported.go

build: fix linting issues reported by running golangci-lint with different GOOS

2024-04-22 19:29:12 +02:00

azureblob.go

azureblob: cleanup uncommitted blocks on upload errors

2025-01-22 11:56:05 +00:00