- Le plus récent
- Le plus de votes
- La plupart des commentaires
[Errno 28] No space left on device is a message more likely to be associated with the device you're running the commands on - is this a server, or an EC2 instance, or your laptop - rather than S3.
Check the local filesystem usage for any full filesystems.
1st I type: aws glacier initiate-job --account-id 7115####8535 --vault-name Cxxxs --job-parameters='{"Type": "inventory-retrieval"}'
then: aws glacier describe-job --account-id 711####535 --vault-name Cxxx --job-id fFWmpU3oc3hc8AEFRwZRDP0AINs-X9NpbF-FrMMB8uWR*****83AUOFb5Ha9SXdAd6h8WCIB_zCSXXSugdDWgGEM65
I keep checking, keep getting "... "Completed": false, "StatusCode": "InProgress",..." for a few hours, then finally get: "StatusCode": "Succeeded", "StatusMessage": "Succeeded",
then I type:
aws glacier get-job-output --account-id 711####535 --vault-name Cxxx --job-id fFWmpU3oc3hc8AEFRwZRDP0AINs-X9NpbF-FrMMB8uW*****3AUOFb5Ha9SXdAd6h8WCIB_zCSXXSugdDWgGEM65 output.json
and get: [Errno 28] No space left on device
The
aws glacier get-job-output
command is trying to write output.json to disk, presumably in the current directory.What's the anticipated size of output.json and is there enough free space in the filesystem? Try both
df -h
anddf -i
just in case it's run out of inodes and not blocks.Also, does the user that is running the command have write privileges to the directory?
Still getting the exact error message using a different machine (with full privilidges and more than enough space) Is there a way to get in touch with a real person who manages these vaults/archives? We've had a nighmare trying to download (& delete) these files that we need to get rid of. Thaks for all of your help
If you are on any support plan other than "Basic" you can create a technical support case here https://support.console.aws.amazon.com/support/home#/case/create
Thanks. I actually upgraded my account last week in hopes of getting answer, but so far its been radio silence,,,
Contenus pertinents
- demandé il y a un an
- demandé il y a 9 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
No, thats not it. I've duplicated the same process (with exact error) on other machines
Could you share the command you're running (obfuscate the bucket name if you prefer) as well as the full error message please.