Solved Fedora Block Device Full How - Extend Partition
-
-
Did you create a partition for the free space? You need to use fdisk to make a third primary partition.
-
@stacksofplates ok, following this here.
-
Dumb question, would it be easier for me to simply add a separate drive, and then extend the root drive into the new drive?
-
@DustinB3403 said in Fedora Block Device Full How - Extend Partition:
Dumb question, would it be easier for me to simply add a separate drive, and then extend the root drive into the new drive?
Maybe.
You can skip the fdisk stuff and add a whole new block device to LVM if you add another virtual disk. -
@Francesco-Provino I'm fine with a separate physical device, so long as the system uses it as a single device.
-
@DustinB3403 said in Fedora Block Device Full How - Extend Partition:
@Francesco-Provino I'm fine with a separate physical device, so long as the system uses it as a single device.
You can actually move everything to the new drive using lvm. Tho I don't remember how to do that offhand, I'd have to look it up.
-
OK so this is what I have with a new "physical" drive attached to this VM.
Where too from here?
-
@DustinB3403 said in Fedora Block Device Full How - Extend Partition:
OK so this is what I have with a new "physical" drive attached to this VM.
Where too from here?
I'm actually doing this now myself, give me a sec.
-
@DustinB3403 pvcreate /dev/xvdb and proceed with vgextend…
-
@Francesco-Provino reading the manual for pvextend
-
@DustinB3403 said in Fedora Block Device Full How - Extend Partition:
@Francesco-Provino reading the manual for pvextend
You don't want to extend a pv tho, you want to create a new one. Add the new pv into the current vg (volume group), and then extend the lv (logical volume) to fill the new pv.
pvcreate /dev/xvdb vgextend fedora /dev/xvdb lvextend -l 100%FREE /dev/fedora/rootSee if that lvextend works, might need to feed it another vg/pv path.
-
-
Thanks guys, I think I've got it.
-
@DustinB3403 Now you need to figure out why your root partition got filled up in the first place!
-
@travisdh1 This was because the person who setup this system configured everything on a tiny partition.
I'm fine with the original size, as all this system does is push our image out. Until now that is, when I need to add a new image to push.
The entire drive is holding 2 windows images.
-
@DustinB3403 said in Fedora Block Device Full How - Extend Partition:
@travisdh1 This was because the person who setup this system configured everything on a tiny partition.
I'm fine with the original size, as all this system does is push our image out. Until now that is, when I need to add a new image to push.
The entire drive is holding 2 windows images.
Ah, the images should've never been included on / (root) in the first place.
-
-
@travisdh1 said in Fedora Block Device Full How - Extend Partition:
@DustinB3403 said in Fedora Block Device Full How - Extend Partition:
@travisdh1 This was because the person who setup this system configured everything on a tiny partition.
I'm fine with the original size, as all this system does is push our image out. Until now that is, when I need to add a new image to push.
The entire drive is holding 2 windows images.
Ah, the images should've never been included on / (root) in the first place.
Exactly. But they are, so without building a new imaging system, I'd rather (and believe I have since fog sees it correctly) is to just add space for the purposes here.
-
@DustinB3403 said in Fedora Block Device Full How - Extend Partition:
@travisdh1 said in Fedora Block Device Full How - Extend Partition:
@DustinB3403 said in Fedora Block Device Full How - Extend Partition:
@travisdh1 This was because the person who setup this system configured everything on a tiny partition.
I'm fine with the original size, as all this system does is push our image out. Until now that is, when I need to add a new image to push.
The entire drive is holding 2 windows images.
Ah, the images should've never been included on / (root) in the first place.
Exactly. But they are, so without building a new imaging system, I'd rather (and believe I have since fog sees it correctly) is to just add space for the purposes here.
Sorry, I was away for a while. You could always add the drive to the mount point where the images are stored. I had a Gitlab server that ran out of space, so I just copied the gitlab data from /var/opt and set the second drive to mount there.
