AWS Storage Gateway User Guide
Your Gateway Performance Declined After
You Performed a Recursive Operation
Your Gateway Performance Declined After You
Performed a Recursive Operation
In some cases, you might perform a recursive operation, such as renaming a directory or enabling
inheritance for an ACL, and force it down the tree. If you do this, file gateway recursively applies the
operation to all objects in the file share.
For example, suppose that you apply inheritance to existing object in an Amazon S3 bucket. file gateway
recursively applies inheritance to all objects in the bucket. Such operations can cause your gateway
performance to decline.
Troubleshooting Volume Issues
You can find information about the most typical issues you might encounter when working with
volumes, and actions that we suggest that you take to fix them.
Topics
•
The Console Says That Your Volume Is Not Configured (p. 331)
•
The Console Says That Your Volume Is Irrecoverable (p. 331)
•
Your Cached Gateway is Unreachable And You Want to Recover Your Data (p. 332)
•
The Console Says That Your Volume Has PASS THROUGH Status (p. 332)
•
You Want to Verify Volume Integrity and Fix Possible Errors (p. 333)
•
Your Volume's iSCSI Target Doesn’t Appear in Windows Disk Management Console (p. 333)
•
You Want to Change Your Volume's iSCSI Target Name (p. 333)
•
Your Scheduled Volume Snapshot Did Not Occur (p. 333)
•
You Need to Remove or Replace a Disk That Has Failed (p. 333)
•
Throughput from Your Application to a Volume Has Dropped to Zero (p. 333)
•
A Cache Disk in Your Gateway Encounters a Failure (p. 334)
•
A Volume Snapshot Has PENDING Status Longer Than Expected (p. 334)
The Console Says That Your Volume Is Not
Configured
If the AWS Storage Gateway console indicates that your volume has a status of UPLOAD BUFFER NOT
CONFIGURED, add upload buffer capacity to your gateway. You cannot use a gateway to store your
application data if the upload buffer for the gateway is not configured. For more information, see
and configure upload buffer or cache storage (p. 223)
The Console Says That Your Volume Is Irrecoverable
For stored volumes, if the AWS Storage Gateway console indicates that your volume has a status of
IRRECOVERABLE, you can no longer use this volume. You can try to delete the volume in the AWS
Storage Gateway console. If there is data on the volume, then you can recover the data when you create
a new volume based on the local disk of the VM that was initially used to create the volume. When you
create the new volume, select
Preserve existing data
. Make sure to delete pending snapshots of the
volume before deleting the volume. For more information, see
. If deleting
the volume in the AWS Storage Gateway console does not work, then the disk allocated for the volume
might have been improperly removed from the VM and cannot be removed from the appliance.
API Version 2013-06-30
331
