Questions tagged with Amazon Elastic Block Store
Content language: English
Sort by most recent
Not able to detach EBS Volume
Although the EBS volume is not attached to any EC2 instsances, it is still showing in-use. I tried force detach from aws console but it is stuck. Force detaching the volume from AWS CLI shows following error ``` An error occurred (InvalidParameterValue) when calling the DetachVolume operation: The volume ID 'vol-00402f84342cf78f' is malformed ```
How can i check files and data stored in EBS volume
Hello members, I am running ec2 instance with 20 GB ebs volume. Actually still i have not stored any files in ebs volume using cpanel but when i am visiting billing dahsboard it showing me 14 GB usage of EBS volume so can anyone tell me where this storage would be used and how can i see its data?
Mounting EBS or EFS as File System in on Premise Instances
I have used the open source[ s3fs](https://github.com/s3fs-fuse/s3fs-fuse) for mounting s3 buckets in a local directory. Are there similar open source solutions for EBS or EFS? Most of the guides I see seem to assume that I am using an EC2 with the appropriate security group setting, but I need it to be on my own VM or laptop (running Ubuntu).
Faster processing: EBS Vs S3
What is the best solution to read data by an application hosted in an EC2 instance using S3 than EBS? I am using an EC2 instance for reading data stored in EBS (size approx. 2 TB) and performing many transformations using ETL and analytics jobs. But as part of strict 3 tier architecture, there is a need to move this data from EBS (application layer) to data tier (preferably S3). My understanding is that if I move all these data permanently from EBS to S3, and read 2TB data from S3 daily for my jobs, the performance of jobs will be very low. 1) Can you please suggest how can I achieve a better approach? 2) Instead of S3, can I use any other service? 3) The system is Linux system and hence I can't use Fsx 4) I need the lightening performance for my jobs. Any help in this regard, will be appreciated.
Can I Use NVMe Reservation on a Multi-Attach Enabled Volume?
Hi, I want to use Amazon EBS Multi-Attach to share data between multiple EC2 instances. In the [UserGuide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volumes-multi.html), it says > Multi-Attach enabled volumes do not support I/O fencing. I/O fencing protocols control write access in a shared storage environment to maintain data consistency. Your applications must provide write ordering for the attached instances to maintain data consistency. I've googled *"I/O fencing"* and found that NVMe Reservation is a good way (compared to "power fencing", which means powering off the error node) to implement I/O fencing. However, I failed to use NVMe Reservation on a Multi-Attach Enabled Volume. The details are as follows. - EC2: r5b.large, ubuntu-22.04 - EBS: io2, 100GiB, 6000 IOPS, enabled Multi-Attach I run following command in ec2 instance: ``` > sudo nvme list ``` and get ``` Node SN Model Namespace Usage Format FW Rev --------------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- -------- /dev/nvme0n1 volxxxxxxxxxxxxxxxx Amazon Elastic Block Store 1 8.59 GB / 8.59 GB 512 B + 0 B 2.0 /dev/nvme1n1 volxxxxxxxxxxxxxxxx Amazon Elastic Block Store 1 107.37 GB / 107.37 GB 512 B + 0 B 2.0 ``` then run ``` > sudo nvme resv-register -n 1 --crkey=0x0 --nrkey=0xa1 --rrega=0 /dev/nvme1n1 ``` and get ``` NVMe status: INVALID_OPCODE: The associated command opcode field is not valid(0x2001) ``` I googled this error message and find that it may be caused by the driver not supporting. To confirm that, I run ``` > sudo nvme amzn id-ctrl /dev/nvme1n1 -H ``` and get ``` ... oncs : 0 [8:8] : 0 Copy Not Supported [7:7] : 0 Verify Not Supported [6:6] : 0 Timestamp Not Supported [5:5] : 0 Reservations Not Supported [4:4] : 0 Save and Select Not Supported [3:3] : 0 Write Zeroes Not Supported [2:2] : 0 Data Set Management Not Supported [1:1] : 0 Write Uncorrectable Not Supported [0:0] : 0 Compare Not Supported ... ``` The fifth bit indicates that "not supporting reservation". So does **NOT** AWS Multi-Attach Enabled Volume support NVMe Reservation? Or there are other ways to solve this problem？
Are All EC2 Instance Level Storage Lost Upon Rebooting the Instance?
Apologies for the noob question. Some readings led me to believe that an instance level EC2 storage will be lost if I reboot. So the questions I have are * If the storage is totally lost, how does a computer even remember anything? Should not it remember at least the username, password, sudo group etc. across reboots? * How to store my codes, configurations in an EC2 instance to be retained across reboots? Is it possible at all, or does it have to be something like an EBS that is decoupled from the instance and must be mounted on every start up? I am intending to use Ubuntu 22.04 as the OS, if that is important.
Mount fails when adding new node to GFS2 EBS multi-attached Clustered storage
Hello, We have setup EBS multi-attach clustered storage as per https://aws.amazon.com/blogs/storage/clustered-storage-simplified-gfs2-on-amazon-ebs-multi-attach-enabled-volumes/ and it is working fine on two EC2 nodes having centos 7 OS. Now we have added 3rd EC2 node to GFS2 EBS Clustered storage, it is getting added fine via command ``` pcs cluster node add <new_ec2_node> --start --enable ``` however mounting of EBS volume fails with error in log as: ``` Failed Resource Actions: * xxx_data_cluster_start_0 on xxx-golan 'unknown error' (1): call=30, status=complete, exitreason='Couldn't mount device [/dev/xxvg/xxlv] as /data', last-rc-change='Tue Nov 8 10:56:47 2022', queued=0ms, exec=2272ms ``` When we manually try to mount EBS multi-attach volume from new node it gives error: ``` mount: mount /dev/mapper/xxxvg-xxxlv on /data failed: Too many users ``` What could be the problem ? Thanks
adding ec2 volume to instance with powershell
I got following script to add a new volume to instanceID. However I am unsure how to get the volume ID after volume creation. Also the DeviceID what should it be? ``` Param ( [string][Parameter(Mandatory) = $True] $InstanceId [string][Parameter(Mandatory = $True)] $driveletter, [int][Parameter(Mandatory = $True)] $size, [string][Parameter(Mandatory) = $True)] $az, [string][Parameter(Mandatory = $True)] $Region, [string][Parameter(Mandatory) = $True] $volumetype New-ec2volume -AvailabilityZone $az -VolumeType $volumetype -size $size -Region $Region Add-EC2Volume -InstanceId $InstanceId ) ```
Can I use multi-attach in Windows
I am trying to decipher the following statement (first bullet from [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volumes-multi.html#considerations)): > You can attach a volume that is Multi-Attach enabled to Windows instances, but the operating system does not recognize the data on the volume that is shared between the instances, which can result in data inconsistency. If OS doesn't recognize the data, then data inconsistency is least of my concerns, no? To summarize can I use multi-attach with Windows? Or the only option is FSx, that requires full-blown AD and therefore drives the price up?
What does the "Snapshot" column indicate? Why is it all the same string?
I would like to know what exactly the Snapshot column on the EBS Volume screen shows. In my environment, I am seeing the same string "snap-0df8908c34e3...." for all volume IDs. ![EBS Volume list view](/media/postImages/original/IMfHE49ep4QN2nfLlzW5OAmQ)
Instance reachability check failed
Hi In the Instance status checks show "Instance reachability check failed" and I am unable to SSH to the Instance. The AWS Compute Optimizer was throwing an error in EBS for reading and write bandwidth, so I decided to upgrade the instance from t2.medium to t3.large, also the hard drive from 8GB to 16GB to gp3. Now It shows Running. But in Status checks, Instance status check shows "Instance reachability check failed". The instance was working fine a few days back. I tried rebooting instance. It doesn't reboot. I start stop and start, that works and shows Running, but same instance status check issue. I tried rescue option mentioned in https://aws.amazon.com/premiumsupport/knowledge-center/ec2-instance-boot-issues/, but still the same issue. Here is the system log ` [ 12.483121] </TASK> [ 12.485967] Kernel Offset: 0x10600000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 12.497046] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]--- `