Skip to main content

저장 장치 추가하기

생성된 EC2 인스턴스에는 운영 체제를 지원하기에 충분한 저장 용량을 갖춘 루트 볼륨과 분석을 지원하는 데 필요한 몇 가지 추가 애플리케이션이 있습니다. 이제 다운로드하려는 대용량 데이터 세트(예: Raw reads, aligned sequences 등)를 수용하기 위해 추가 스토리지가 필요합니다. 따라서 추가 스토리지를 연결해야 합니다.

이 섹션에서는 다음과 같이 설명합니다:

a. EBS(Elastic Block Store) 볼륨을 생성합니다.

b. 새 볼륨을 EC2 인스턴스에 연결합니다.

c. 새 볼륨을 포맷하고 마운트합니다.

    1. 파일 시스템으로 새 볼륨을 포맷합니다.

    2. 볼륨을 마운트하고 일부 데이터를 복사합니다.

EBS 볼륨 만들기

  1. AWS 관리 콘솔 검색 창에 EC2를 입력하여 EC2 서비스로 이동합니다.

     

  2. 왼쪽 탐색 표시줄에서 Elastic Block Store 아래의 Volumes을 클릭합니다.

Screenshot 2023-09-27 at 10.19.25 AM.png

  1. Create Volume (오른쪽 상단 모서리)를 클릭하여 새 볼륨을 만듭니다.

     

  2. Create Volume 페이지에서 볼륨의 필요한 크기(예: 데이터 세트 크기에 따라 10GB 이상)를 GB 단위로 입력합니다.

이 실습에서는 10GB면 충분합니다.
중요: Availability Zone 이 볼륨을 연결할 EC2 인스턴스와 동일한지 확인하세요.

Screenshot 2023-09-27 at 10.21.34 AM.png

Screenshot 2023-09-27 at 10.22.23 AM.png

  1. Add Tag를 클릭하여 리소스에 고유한 태그를 지정합니다. 키에 '이름'을 입력하고 값에 '[your initials]-EBS'를 입력합니다.


    Screenshot 2023-09-27 at 10.23.27 AM.png

실행 중인 인스턴스에 EBS 볼륨 연결하기

  1. On the Left Navigation Bar click on Volumes under Elastic Block Store to view all the volumes. Select your newly created volume searching the list for the unique Name tag provided in the previous step.


    Screenshot 2023-09-27 at 10.24.55 AM.png

  1. Click on Actions and further click on Attach Volume

  2. In the Attach Volume dialog, click on the Instance field and select the EC2 instance by looking for the Instance ID or Name Tag in the list. Click Attach to attach the volume.

Screenshot 2023-09-27 at 10.25.54 AM.png

If attached successfully - In the list of displayed volumes you should see your new volume having a status (under the State Column) indicating In Use.

Screenshot 2023-09-27 at 10.26.22 AM.png

  1. On the left Navigation pane click EC2 Dashboard on the very top of the list of items.

  2. Select Instances (running) and then select your EC2 Instance from the list of instances to which you attached the Volume.

Screenshot 2023-09-27 at 10.27.08 AM.png

Important: Note down the specific device name for the next step of mounting the volume. The drive name may differ from what’s shown.

NOTE: Depending on the Linux version and the machine type, the device names may differ. The EC2 Console will generally show /dev/sdX, where X is a lower-case letter, but you may see /dev/xvdX or /dev/nvmeYn1. The following table may help with translating. Another way to help track is to pick different sizes for your EBS volumes (such as 151, 152, 153 GB for different volumes). | Device name (Console) | Alternate 1 | Alternate 2 | | — | — | — | | /dev/sda | /dev/xvda | /dev/nvme0n1 | | /dev/sdb | /dev/xvdb | /dev/nvme1n1 | | /dev/sdc | /dev/xvdc | /dev/nvme2n1 | | /dev/sdd | /dev/xvdd | /dev/nvme3n1 | | /dev/sde | /dev/xvde | /dev/nvme4n1 | | /dev/sdf | /dev/xvdf | /dev/nvme5n1 |

볼륨 마운트

  1. Log in to your EC2 Instance.

  2. List the available disks using the following command:

lsblk

The output will list the disks attached to your instance.

예시

Screenshot 2023-09-27 at 10.30.52 AM.png

NOTE: Depending on the Linux version and the machine type, the device names may differ. The EC2 Console will generally show /dev/sdX, where X is a lower-case letter, but you may see /dev/xvdX or /dev/nvmeYn1. The following table may help with translating. Another way to help track is to pick different sizes for your EBS volumes (such as 151, 152, 153 GB for different volumes).

Device name (Console) Alternate 1 Alternate 2
/dev/sda /dev/xvda /dev/nvme0n1
/dev/sdb /dev/xvdb /dev/nvme1n1
/dev/sdc /dev/xvdc /dev/nvme2n1
/dev/sdd /dev/xvdd /dev/nvme3n1
/dev/sde /dev/xvde /dev/nvme4n1
/dev/sdf /dev/xvdf /dev/nvme5n1
  1. Check for an unmounted filesystem of size 100GB. For example: “nvme1n1” as shown below:
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
nvme0n1     259:0    0  150G  0 disk
└─nvme0n1p1 259:1    0  150G  0 part /
nvme1n1     259:2    0   100G  0 disk
  1. Check if the volume has any data using the following command:
sudo file -s /dev/nvme1n1

Where “nvme1n1” is the device you noted from the previous section after attaching the device to the EC2 Instance.

If the above command output shows "/dev/nvme1n1: data", it means your volume is empty.

예시)

Screenshot 2023-09-27 at 10.30.43 AM.png

  1. Format the volume to the ext4 filesystem using the following command.
sudo mkfs -t ext4 /dev/nvme1n1

NOTE: This file-system formatting step is only for a new device, DO NOT run this step while mounting an existing volume as it will wipe out all data on the device.

예시)

Screenshot 2023-09-27 at 10.32.11 AM.png

  1. Create a directory of your choice to mount our new ext4 volume. Let’s use the name “volume1”.
sudo mkdir /mnt/volume1
  1. Mount the volume to “volume1” directory using the following command.
sudo mount /dev/nvme1n1 /mnt/volume1
  1. cd into the volume1 directory and check the disk space for confirming the volume mount.
cd /mnt/volume1
df -h .

The above command would show the free space in the volume1 directory.

  1. At this point, the drive is owned by root and not user. We will want to change ownership of the drive, so that you can change the contents of the drive (Add/remove files, etc).
sudo chown -R ubuntu /mnt/volume1

예시)

Screenshot 2023-09-27 at 10.33.16 AM.png

Screenshot 2023-09-27 at 10.33.48 AM.png

  1. For your own information, it is possible to later remove this device. Practice unmounting, then remounting it. To unmount the volume, you have to use the following command. Make sure to be outside the directory to unmount the volume.
sudo umount /dev/nvme1n1

But we’ll need this device for later, so remember to re-mount it.

sudo mount /dev/nvme1n1 /mnt/volume1

Back to top