New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'content-length' error when trying to synccopy
blob container items to a file share
#108
Comments
I believe your command is malformed, try: blobxfer synccopy --storage-account [sa1] --sas [blob-container-sas] --remote-path blob-container --sync-copy-dest-storage-account [sa2] --sync-copy-dest-sas [file-share-sas] --sync-copy-dest-remote-path file-share --sync-copy-dest-mode file --no-server-side-copy A few notes:
|
- --storage-url was not accepted - --sync-copy-dest-storage-url destination mode was not being properly percolated - Add additional synccopy auth limitations to docs - Resolves #108
Thanks for the fast response! I tried your command, it appeared to fail differently:
So I dropped the explicit
Some more context around what I'm attempting to do:
Thanks - that could be a simpler option! |
Apologies, I forgot to include the important parameter:
By default, it will try to use server side copy, but that is not supported to an Azure File destination. |
Closing, please re-open if issue has not been solved. |
Problem Description
First time
blobxfer
user here. Apologies if I'm holding it wrong!I'm trying to copy the contents of a blob container to a file share within the same storage account.
Not sure if this is supported as I'm also having trouble with using
AzCopy
for the same task?Azure blobxfer parameters output
Steps to Reproduce
storage-account
, with a blob containerblob-container
and a file share calledfile-share
AZ_SAS_TOKEN
blob-container
intofile-share
using the following commandObserve the attached error logs
Expected Results
The file
testfile.txt
is copied tofile-share
and containsabcd
Actual Results
testfile.txt
isn't written tofile-share
Additional Logs
The text was updated successfully, but these errors were encountered: