LinuxQuestions.org - How to extending /dev/mapper/fedora-data to take up spar/unused space

- Fedora (https://www.linuxquestions.org/questions/fedora-35/)

- - How to extending /dev/mapper/fedora-data to take up spar/unused space (https://www.linuxquestions.org/questions/fedora-35/how-to-extending-dev-mapper-fedora-data-to-take-up-spar-unused-space-4175450754/)

How to extending /dev/mapper/fedora-data to take up spar/unused space

Hi all,

Fedora 18 desktop 64bit, newly installed

The capacity of the HD is 2TB

$ df -h

Code:

Filesystem                Size  Used Avail Use% Mounted on

devtmpfs                    16G    0  16G  0% /dev

tmpfs                      16G  4.7M  16G  1% /dev/shm

tmpfs                      16G  9.4M  16G  1% /run

tmpfs                      16G    0  16G  0% /sys/fs/cgroup

/dev/mapper/fedora-root00  97G  4.3G  87G  5% /

tmpfs                      16G  20K  16G  1% /tmp

/dev/sda1                  236M  138M  86M  62% /boot

/dev/mapper/fedora-data    1.5T  470G  900G  35% /data

$ sudo fdisk -l

Code:



Disk /dev/sda: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00064d3a



  Device Boot      Start        End      Blocks  Id  System

/dev/sda1  *        2048      499711      248832  83  Linux

/dev/sda2          499712  3279364095  1639432192  8e  Linux LVM



Disk /dev/sdb: 120.0 GB, 120034123776 bytes, 234441648 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x000cde8a



  Device Boot      Start        End      Blocks  Id  System

/dev/sdb1  *        2048      499711      248832  83  Linux

/dev/sdb2          501758  234440703  116969473    5  Extended

/dev/sdb5          501760  234440703  116969472  8e  Linux LVM



Disk /dev/mapper/fedora-swap: 1048 MB, 1048576000 bytes, 2048000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes





Disk /dev/mapper/fedora-root00: 104.9 GB, 104857600000 bytes, 204800000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes





Disk /dev/mapper/localhost-root: 85.5 GB, 85513469952 bytes, 167018496 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes





Disk /dev/mapper/localhost-swap_1: 34.3 GB, 34259075072 bytes, 66912256 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes





Disk /dev/mapper/fedora-data: 1572.9 GB, 1572864000000 bytes, 3072000000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

I shall use this PC for virtualization running Oracle VirtualBox.

There are some spare space on the HD not used/installed. Pls advise;

1)
How to expand /dev/mapper/fedora-data taking up the rest unused space instead of reinstalling the complete system?

OR

2)
Another thought:-
At the present moment I don't need such a big space on /dev/mapper/fedora-data. What/How shall I use the spare/uninstalled space, now or in future?

TIA

B.R.
satimis

There are several options.
You can resize the LVM partition to use the unallocated space and then resize the logical volumes as desired.
You can create a regular partition.
You can create another LVM partition with logical volumes and add the space to any of the existing LVs

Fedora has a GUI LVM tool and you can modify LVs on the fly without rebooting.

Quote:

Originally Posted by michaelk (Post 4895076)

Hi,

Tks for your advice.

My original setup on the HD was making it dualboot leaving some space for testing clouds. Because some of them need bare metal to run. Now I'm prepared abandoning such an arrangement. Because I found several spare old HDs, 180G, 500G and 600G. I can use them testing cloud.

Frankly speaking 1.5T space on /dev/mapper/fedora-data is more than sufficient for my use including in the foreseeable future.

Leave the unalloted space there?

To resize /dev/mapper/fedora-data won't take me lot of work nor any risk. Because this is a new box without data on it. In the worst case if something goes wrong on resizing I just reinstall Fedora. But if there are VMs running on it, there will be lot of work to do in resizing /dev/mapper/fedora-data.

Oh, Yes. The Fedora installer has a wonderful tool resizing LVs on the fly. I almost forgot it. Several months back I ran it resizing HD making the latter dualboot. Ubuntu 12.04 was running on the HD occupying the entire HD capacity. I ran Fedora installer resizing the HD to install Fedora on the space obtained. Wonderful, it was very easy without failure. I did it at least 3~4 times.

B.R.
satimis