Skip to main content

Creating a Partition Larger Than 2 TB

If you want to create a partition larger than 2 TB on a linux operating system, fdisk utility will not cover your need. Parted is a good partitioning editor and may help you to create a partition larger than 2 TB.

Here is a step by step example of creating 4 TB partition:

In this example, physical disk name is sdh.

First we can check size of the disk: (third tab shows the size and we can calculate it in megabytes by dividing 1024, 4392296448/1024 = 4289352 )

# more /proc/partitions |grep sdh
8   112 4392296448 sdh

Run parted:
# parted /dev/sdh

In parted prompt, print command displays the partition table selected device :
(parted) print
Disk geometry for /dev/sdh: 0.000-4289352.000 megabytes
Disk label type: gpt
Minor    Start       End     Filesystem  Name                  Flags

As shown, there is no partition configured.
Disk label can be set by typing mklabel:
(parted) mklabel gpt

mkpart is used creating the partition:
(parted) mkpart primary 0 4289352

We can confirm that the partition is created by typing:
(parted) print
Disk geometry for /dev/sdh: 0.000-4289352.000 megabytes
Disk label type: gpt
Minor    Start       End                  Filesystem  Name              Flags
1             0.017     4289351.983

We can quit:
(parted) quit

To format the partition:
# mkfs.ext3 /dev/sdh1

Now, we have a formatted 4 TB disk partition to use.

Comments

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three

3 Node (Master Slave Slave) Redis Cluster with Sentinel

It is possible to make your Redis cluster Fault Tolerant and Highly Available by building a replica set and then monitor these nodes using sentinel for automatic failover. I am going to give an example setup to explain it. The structure is built with three nodes running one as a master and two as slaves. Master Node: (Centos 7.2) 192.168.1.11 Slave1 Node: (Centos 7.2) 192.168.1.12 Slave2 Node: (Centos 7.2) 192.168.1.13 Edit System settings on each node: /etc/sysctl.conf Disable transparent hugepage (transparent_hugepage=never) on each node: /etc/default/grub Apply grub config and reboot each node: Master Node: /etc/redis/6379.conf Slave1 Node: /etc/redis/6379.conf Slave2 Node: /etc/redis/6379.conf Master Node: /etc/redis/sentinel.conf Slave1 Node: /etc/redis/sentinel.conf Slave2 Node: /etc/redis/sentinel.conf Each Node: /etc/systemd/system/multi-user.target.wants/redis-server.service Each Node: /etc/