Skip to main content

Create File system and Partition table to newly attached EBS volume

Create EBS volume on the same zone of EC2 instance created

Attach the EBS volume to the EC2 instance


# cat /proc/partitions

major minor  #blocks  name

 202        1    8388608 xvda1
 202       80    1048576 xvdf
 202       96    1048576 xvdg


# lsblk

NAME  MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvdf  202:80   0   1G  0 disk /mnt/my-data
xvdg  202:96   0   1G  0 disk
xvda1 202:1    0   8G  0 disk /

# df -h

Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1      7.8G  1.1G  6.7G  14% /
devtmpfs        282M   20K  282M   1% /dev
tmpfs           297M     0  297M   0% /dev/shm
/dev/xvdf      1008M   34M  924M   4% /mnt/my-data for xvdf  referenced in # lsblk output above

# sudo mkdir /u02 -- Create directory

# mkfs.ext3 /dev/xvdg  -- Create filesystem for /dev/xvdg

# sudo mount /dev/xvdg /u02 -- mount newly created file system

# df -h

Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1      7.8G  1.1G  6.7G  14% /
devtmpfs        282M   20K  282M   1% /dev
tmpfs           297M     0  297M   0% /dev/shm
/dev/xvdf      1008M   34M  924M   4% /mnt/my-data
/dev/xvdg      1008M   34M  924M   4% /u02


Comments

Popular posts from this blog

What is the difference between Elastic and Enterprise Redis w.r.t "Hybrid Query" capabilities

  We'll explore scenarios involving nested queries, aggregations, custom scoring, and hybrid queries that combine multiple search criteria. 1. Nested Queries ElasticSearch Example: ElasticSearch supports nested documents, which allows for querying on nested fields with complex conditions. Query: Find products where the product has a review with a rating of 5 and the review text contains "excellent". { "query": { "nested": { "path": "reviews", "query": { "bool": { "must": [ { "match": { "reviews.rating": 5 } }, { "match": { "reviews.text": "excellent" } } ] } } } } } Redis Limitation: Redis does not support nested documents natively. While you can store nested structures in JSON documents using the RedisJSON module, querying these nested structures with complex condi...

Training LLM model requires more GPU RAM than storing same LLM

Storing an LLM model and training the same model both require memory, but the memory requirements for training are typically higher than just storing the model. Let's dive into the details: Memory Requirement for Storing the Model: When you store an LLM model, you need to save the weights of the model parameters. Each parameter is typically represented by a 32-bit float (4 bytes). The memory requirement for storing the model weights is calculated by multiplying the number of parameters by 4 bytes. For example, if you have a model with 1 billion parameters, the memory requirement for storing the model weights alone would be 4 GB (4 bytes * 1 billion parameters). Memory Requirement for Training: During the training process, additional components use GPU memory in addition to the model weights. These components include optimizer states, gradients, activations, and temporary variables needed by the training process. These components can require additional memory beyond just storing th...

How are vector databases used?

  Vector Databases Usage: Typically used for vector search use cases such as visual, semantic, and multimodal search. More recently, they are paired with generative AI text models for conversational search experiences. Development Process: Begins with building an embedding model designed to encode a corpus (e.g., product images) into vectors. The data import process is referred to as data hydration. Application Development: Application developers utilize the database to search for similar products. This involves encoding a product image and using the vector to query for similar images. k-Nearest Neighbor (k-NN) Indexes: Within the model, k-nearest neighbor (k-NN) indexes facilitate efficient retrieval of vectors. A distance function like cosine is applied to rank results by similarity.