Linux : Fdisk vs Parted paritioning tools

 

When to Use fdisk and parted in Linux?

fdisk vs parted - Compared

Both fdisk and parted are partitioning tools in Linux, but they serve different purposes and support different disk types.

Use fdisk When:

  • You are working with MBR (Master Boot Record) partitioned disks (older partitioning scheme).
  • The disk size is less than 2 TB (MBR supports a maximum of 2 TB).
  • You need a simple, command-line-based tool for partitioning.
  • You are dealing with legacy systems that don’t support GPT.

Example:

sudo fdisk /dev/sdb

Use parted When:

  • You are working with GPT (GUID Partition Table) partitioned disks (modern partitioning scheme).
  • The disk size is greater than 2 TB (GPT supports up to 9.4 ZB).
  • You need to create more than four primary partitions (MBR allows only four).
  • You want a scriptable, flexible tool that supports both MBR and GPT.
  • You are working on modern Linux distributions where GPT is preferred.

Example:

sudo parted /dev/sdb

Then inside parted, you can create a new GPT partition:

mklabel gpt
mkpart primary ext4 1MiB 100%

Conclusion

  • Use fdisk for MBR partitions and smaller disks (< 2 TB).
  • Use parted for GPT partitions and large disks (> 2 TB).
  • If you're setting up a new system with a modern disk, parted with GPT is usually the best choice.

(Refer next blog to know more about MBR and GPT.

Thank you 




=======================================================================
Thank you, check out more blogs for such information..!
For any queries,feel free to reach out me on shubhammore07007@gmail.com

Comments

Post a Comment

Popular posts from this blog

Nginx : Setting Up Nginx with Load Balancing

Image
This guide explains how to configure Nginx as a load balancer for multiple backend applications running on different ports. The setup includes three application servers running on ports 8001, 8002, and 8003, with Nginx balancing requests among them.   Nginx Configuration Details Individual Server Blocks Each backend application is configured as an independent Nginx server block: Server 1 Configuration ( server1.conf ) [root@server1 conf.d]# cat /etc/nginx/conf.d/server1.conf | grep -v "#"   server { listen 8001; server_tokens off; server_name _; client_max_body_size 35M; charset utf-8; large_client_header_buffers 4 16k; root /usr/share/nginx/server1; index index.html index.php index.cgi; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; } Server 2 Configuration ( server2.conf ) [root@server1 conf.d]# cat /etc/nginx/conf.d/server2.conf | grep -v "#"     server { listen 8002; server_tokens off;...
Read more

Nginx : Virtual hosting using Location directives

Image
This setup demonstrates a virtual container-based environment in Nginx where multiple locations are configured under a single server block, rather than a load-balancing mechanism. Each location serves a different application based on its respective directory structure. Nginx Configuration Server Configuration server { listen 80; server_tokens off; server_name _; client_max_body_size 35M; charset utf-8; large_client_header_buffers 4 16k; root /usr/share/nginx/server1; index index.html index.php index.cgi; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; location /server2 { root /usr/share/nginx/; index index.html index.php index.cgi; access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; } location /server3 { root /usr/share/nginx/; index index.html index.php index.cgi; access_log /var/log/nginx/access.log; error_log /...
Read more

Terraform project with AWS to build infra within seconds! (Web Ec2 with eIP)

Image
1. Introduction: What is Terraform? Terraform is an open-source Infrastructure as Code (IaC) tool created by HashiCorp. It lets you define, provision, and manage cloud infrastructure using declarative configuration files . Instead of manually creating AWS resources in the console, you write code that describes what you want, and Terraform takes care of creating or updating it. Why use it with AWS? a) Infrastructure as Code (IaC) You can define AWS resources (EC2, VPC, S3, IAM, etc.) in .tf files. These configurations can be version-controlled in Git. b) Multi-Cloud Support Although AWS has its own tool (CloudFormation), Terraform works with AWS + Azure + GCP + on-prem at the same time. c) Reusability & Automation You can reuse Terraform modules to deploy the same AWS setup in different environments (dev, test, prod). d) State Management Terraform keeps a state file to know which resources it manages. Makes it easy to track and update changes in AWS without accidentally del...
Read more