Before you begin with partitions, make sure you have a solid backup solution in place. Check MSP360 Free Backup software<\/a> for Linux: a command-line based solution designed to automate file-level backups.<\/p><\/blockquote>\n The primary way of resizing drive partitions in Linux is to delete the old one and create a new one, using the previous starting sector (you can think about it like \u201cleft bound of the new partition\u201d). Then you need to simply modify the file system properties to fit the new bounds. If done carefully, you will not lose your data on the modified element<\/b>, despite the frightening phrase \"delete the partition\".<\/p>\n Linux has built-in tools (commands) to work with partitions:<\/p>\n In this example, we are going to use Ubuntu Server 14 as an instance in Amazon EC2 cloud. So, the disk we are working with is a block EBS device called \/dev\/xvdb.<\/p>\n Note: depending on your Linux distribution and available storage devices, volume and drive names can be different. You have also use the <\/i>sudo<\/i><\/b> command if your current account doesn\u2019t have \u201croot\u201d privileges.<\/i><\/p>\n First of all, let\u2019s find the partition we want to resize. Use df -h<\/b> command to list available elements:<\/p>\n You can check it using, for example, the lsblk<\/b> tool (for block-level devices only):<\/p>\n I have created the file file_should_remain.test<\/b> to check whether the partition did not lose its data<\/p>\n We need to unmount the volume before modifications - just run the umount <mounting point><\/b> command, where mounting point<\/b> is a file system\u2019s representation of the device. And don\u2019t forget sudo<\/b> to get appropriate permissions:<\/p>\n Now run fdisk<\/b> command with our test disk name as an argument and then type \u201cp\u201d to print the list:<\/p>\n The last line contains important info about the current partition size and its bounds: \u201cStart\u201d and \u201cEnd\u201d. Remember \u201cStart\u201d value (2048 in this example). Now delete this partition by typing \u201cd\u201d and then type \u201cw\u201d to save these modifications:<\/p>\n After the old partition is removed we need to create the new one, either a bigger or smaller size. The following procedure is the same for both actions, but keep in mind that:<\/p>\n In our example, the new partition will be a smaller size so the Shrink<\/b> operation will be performed. Let\u2019s run fdisk<\/b> again and type \u201cn\u201d - creating the new one:<\/p>\n You may use default values in most fdisk questions, but carefully check these highlighted on the picture above: first sector (starting point) and last sector. You can use the +<size>G<\/b> format to specify the desired partition size in Gigabytes (use \u201cM\u201d for Megabytes). Finish by typing \u201cw\u201d to save changes.<\/p>\n Now we need to verify consistency by running e2fsck<\/b>:<\/p>\n Note the highlighted line - the tool shows that there is a mismatch in the file system configuration and current size. This is due to shrinking the partition with no changes made to the file system metadata. Just answer \u201cno\u201d to continue checking.<\/p>\n Let\u2019s fix the error using resize2fs<\/b> and then check the filesystem again:<\/p>\n Now the file system block size is the same as for partition configuration. Finally, let\u2019s mount the resized volume and check that our data is still here:<\/p>\n As you can see, our test file is still here and the partition has a new size.<\/p>\n That's it. Now you have fresh-new partitions.<\/p>\n Keep reading on how to find your AWS access key ID and secret access key<\/a>, why Amazon's EC2 and S3 are fundamentally different types of service, <\/a>Exchange Online vs. Exchange On-Premises<\/span><\/a>,\u00a0<\/span>immutable backups<\/a>,\u00a0what is RMM<\/a>, cost-effective backup solutions<\/a>, what is backup software<\/a>, and an overview of SQL Server backup types<\/a>.\u00a0If you have any questions or comments regarding the article, let us know.<\/p>\n","protected":false},"excerpt":{"rendered":" In this article, we will overview how to resize a partition in a Linux. We will use only built-in tools and commands.<\/p>\n","protected":false},"author":46,"featured_media":28440,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[877,885],"tags":[],"class_list":["post-28432","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-articles","category-other"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/28432","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/users\/46"}],"replies":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/comments?post=28432"}],"version-history":[{"count":12,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/28432\/revisions"}],"predecessor-version":[{"id":60763,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/28432\/revisions\/60763"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/media\/28440"}],"wp:attachment":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/media?parent=28432"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/categories?post=28432"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/tags?post=28432"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Preparation<\/h2>\n
\n
\n
![\"CTA\"](\"https:\/\/no-cache.hubspot.com\/cta\/default\/5442029\/8e06a2b5-4126-47b5-a276-f21b9cf3140d.png\")
<\/a><\/span><\/span>\n<\/div>\n<\/div>\n![\"WP](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2019\/09\/Group-2-19.png\")
<\/div>\n<\/div>\nShrinking or Extending Linux Partition<\/h2>\n
![\"Resize](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-1.png\")
\nThe last line contains the device \/dev\/xvdb1<\/b> - it is our working partition. Note that there are actually 2 names:<\/p>\n\n
![\"Resize](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-2.png\")
<\/p>\n![\"Resize](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-3.png\")
<\/p>\n![\"Resize](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-4.png\")
<\/p>\n![\"Resize](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-5.png\")
<\/p>\n![\"Resize](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-6.png\")
<\/p>\n\n
![\"Resize](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-7.png\")
<\/p>\n![\"Resize](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-8.png\")
<\/p>\n![\"Linux](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-9.png\")
<\/p>\n![\"Resize](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2018\/04\/Linux-partition-resize-10.png\")
<\/p>\nConclusion<\/h2>\n