Resize EBS with LVM Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionHow to identify LVM-over-LUKS or LUKS-over-LVMHow to mount sdb directly or using LVM partitions on sda?Lost space in LVMXen domU not resizing diskUnwrapping an LVM2 recurrence?Extend partition using LVMmultiple encrypted EBS volumes and LVMWindows overrode a LVM pv metadataAmazon EBS - extend LVM partition (non destructively)Optimal LVM Setup to Keep Adding Space to Single Mountpoint
Is there a "higher Segal conjecture"?
What are the pros and cons of Aerospike nosecones?
What are the motives behind Cersei's orders given to Bronn?
Why does Python start at index -1 when indexing a list from the end?
Single word antonym of "flightless"
Can Pao de Queijo, and similar foods, be kosher for Passover?
Is above average number of years spent on PhD considered a red flag in future academia or industry positions?
Do you forfeit tax refunds/credits if you aren't required to and don't file by April 15?
Gastric acid as a weapon
Should I discuss the type of campaign with my players?
G-Code for resetting to 100% speed
Did Xerox really develop the first LAN?
Output the ŋarâþ crîþ alphabet song without using (m)any letters
Why is black pepper both grey and black?
What is the longest distance a 13th-level monk can jump while attacking on the same turn?
How to bypass password on Windows XP account?
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
What LEGO pieces have "real-world" functionality?
Is there a concise way to say "all of the X, one of each"?
Should I call the interviewer directly, if HR aren't responding?
What makes black pepper strong or mild?
How to find all the available tools in macOS terminal?
Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?
What's the purpose of writing one's academic bio in 3rd person?
Resize EBS with LVM
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionHow to identify LVM-over-LUKS or LUKS-over-LVMHow to mount sdb directly or using LVM partitions on sda?Lost space in LVMXen domU not resizing diskUnwrapping an LVM2 recurrence?Extend partition using LVMmultiple encrypted EBS volumes and LVMWindows overrode a LVM pv metadataAmazon EBS - extend LVM partition (non destructively)Optimal LVM Setup to Keep Adding Space to Single Mountpoint
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
AWS supports live EBS resize. I increased from 10G to 20G on my /dev/sdb1
.
Step 1: pvresize /dev/sdb1
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 10G 0 disk
├─xvda2 202:2 0 10G 0 part /
└─xvda1 202:1 0 1M 0 part
xvdb 202:16 0 20G 0 disk
└─xvdb1 202:17 0 10G 0 part
├─home_vol 253:0 0 2G 0 lvm /home
├─tmp_vol 253:0 0 2G 0 lvm /tmp
....
Step 2: pvdisplay
, lvdisplay
pvdisplay
--- Physical volume ---
PV Name /dev/sdb1
VG Name my_vg
PV Size <2.00 GiB / not usable 0
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2559
Free PE 0
Allocated PE 2559
PV UUID ofH9ti-Wcuo-Io4o-796q-q7s8-9Z6S-oDsoEp
and
--- Logical volume ---
LV Path /dev/my_vg/home_vol
LV Name home_vol
VG Name my_vg
LV Status available
# open 1
LV Size <10.00 GiB
Current LE 511
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4
As you see, the number hasn't changed. All right... let's do lvresize
.
Step 3: lvresize -L 10G /dev/my_vg/home_vol
I got this instead:
Insufficient free space: 2049 extents needed, but only 0 available
What step am I missing?
lvm aws
add a comment |
AWS supports live EBS resize. I increased from 10G to 20G on my /dev/sdb1
.
Step 1: pvresize /dev/sdb1
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 10G 0 disk
├─xvda2 202:2 0 10G 0 part /
└─xvda1 202:1 0 1M 0 part
xvdb 202:16 0 20G 0 disk
└─xvdb1 202:17 0 10G 0 part
├─home_vol 253:0 0 2G 0 lvm /home
├─tmp_vol 253:0 0 2G 0 lvm /tmp
....
Step 2: pvdisplay
, lvdisplay
pvdisplay
--- Physical volume ---
PV Name /dev/sdb1
VG Name my_vg
PV Size <2.00 GiB / not usable 0
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2559
Free PE 0
Allocated PE 2559
PV UUID ofH9ti-Wcuo-Io4o-796q-q7s8-9Z6S-oDsoEp
and
--- Logical volume ---
LV Path /dev/my_vg/home_vol
LV Name home_vol
VG Name my_vg
LV Status available
# open 1
LV Size <10.00 GiB
Current LE 511
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4
As you see, the number hasn't changed. All right... let's do lvresize
.
Step 3: lvresize -L 10G /dev/my_vg/home_vol
I got this instead:
Insufficient free space: 2049 extents needed, but only 0 available
What step am I missing?
lvm aws
add a comment |
AWS supports live EBS resize. I increased from 10G to 20G on my /dev/sdb1
.
Step 1: pvresize /dev/sdb1
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 10G 0 disk
├─xvda2 202:2 0 10G 0 part /
└─xvda1 202:1 0 1M 0 part
xvdb 202:16 0 20G 0 disk
└─xvdb1 202:17 0 10G 0 part
├─home_vol 253:0 0 2G 0 lvm /home
├─tmp_vol 253:0 0 2G 0 lvm /tmp
....
Step 2: pvdisplay
, lvdisplay
pvdisplay
--- Physical volume ---
PV Name /dev/sdb1
VG Name my_vg
PV Size <2.00 GiB / not usable 0
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2559
Free PE 0
Allocated PE 2559
PV UUID ofH9ti-Wcuo-Io4o-796q-q7s8-9Z6S-oDsoEp
and
--- Logical volume ---
LV Path /dev/my_vg/home_vol
LV Name home_vol
VG Name my_vg
LV Status available
# open 1
LV Size <10.00 GiB
Current LE 511
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4
As you see, the number hasn't changed. All right... let's do lvresize
.
Step 3: lvresize -L 10G /dev/my_vg/home_vol
I got this instead:
Insufficient free space: 2049 extents needed, but only 0 available
What step am I missing?
lvm aws
AWS supports live EBS resize. I increased from 10G to 20G on my /dev/sdb1
.
Step 1: pvresize /dev/sdb1
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 10G 0 disk
├─xvda2 202:2 0 10G 0 part /
└─xvda1 202:1 0 1M 0 part
xvdb 202:16 0 20G 0 disk
└─xvdb1 202:17 0 10G 0 part
├─home_vol 253:0 0 2G 0 lvm /home
├─tmp_vol 253:0 0 2G 0 lvm /tmp
....
Step 2: pvdisplay
, lvdisplay
pvdisplay
--- Physical volume ---
PV Name /dev/sdb1
VG Name my_vg
PV Size <2.00 GiB / not usable 0
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2559
Free PE 0
Allocated PE 2559
PV UUID ofH9ti-Wcuo-Io4o-796q-q7s8-9Z6S-oDsoEp
and
--- Logical volume ---
LV Path /dev/my_vg/home_vol
LV Name home_vol
VG Name my_vg
LV Status available
# open 1
LV Size <10.00 GiB
Current LE 511
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4
As you see, the number hasn't changed. All right... let's do lvresize
.
Step 3: lvresize -L 10G /dev/my_vg/home_vol
I got this instead:
Insufficient free space: 2049 extents needed, but only 0 available
What step am I missing?
lvm aws
lvm aws
asked 11 hours ago
CppLearnerCppLearner
210310
210310
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You've partitioned xvdb, and your LVM physical volume is on the first partition (which is still only 10GB). So you need to:
- Resize the partition to fill the disk
- Run
pvresize
to pick up the new size.
Personally, on Google Compute instances with LVM, I don't bother partitioning the disk — it serves no real purpose and makes resize much harder. I'd guess the same applies to Amazon. Just put the PV on the full block device (xvdb instead of xvdb1). Then you just have to run pvresize
.
To resize the partition, use your favorite partition table editor. You probably have to delete the partition and create a new one making sure the start sector stays the same. That is extremely important; being a single sector off means losing your data. Then partprobe or kpartx might be able to load the updated table into the kernel with it live, otherwise a reboot is required.
Another alternative is presumably just to attach a third virtual disk, and put another PV there. You can add it to the same volume group, and grow your LVs that way.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f512620%2fresize-ebs-with-lvm%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You've partitioned xvdb, and your LVM physical volume is on the first partition (which is still only 10GB). So you need to:
- Resize the partition to fill the disk
- Run
pvresize
to pick up the new size.
Personally, on Google Compute instances with LVM, I don't bother partitioning the disk — it serves no real purpose and makes resize much harder. I'd guess the same applies to Amazon. Just put the PV on the full block device (xvdb instead of xvdb1). Then you just have to run pvresize
.
To resize the partition, use your favorite partition table editor. You probably have to delete the partition and create a new one making sure the start sector stays the same. That is extremely important; being a single sector off means losing your data. Then partprobe or kpartx might be able to load the updated table into the kernel with it live, otherwise a reboot is required.
Another alternative is presumably just to attach a third virtual disk, and put another PV there. You can add it to the same volume group, and grow your LVs that way.
add a comment |
You've partitioned xvdb, and your LVM physical volume is on the first partition (which is still only 10GB). So you need to:
- Resize the partition to fill the disk
- Run
pvresize
to pick up the new size.
Personally, on Google Compute instances with LVM, I don't bother partitioning the disk — it serves no real purpose and makes resize much harder. I'd guess the same applies to Amazon. Just put the PV on the full block device (xvdb instead of xvdb1). Then you just have to run pvresize
.
To resize the partition, use your favorite partition table editor. You probably have to delete the partition and create a new one making sure the start sector stays the same. That is extremely important; being a single sector off means losing your data. Then partprobe or kpartx might be able to load the updated table into the kernel with it live, otherwise a reboot is required.
Another alternative is presumably just to attach a third virtual disk, and put another PV there. You can add it to the same volume group, and grow your LVs that way.
add a comment |
You've partitioned xvdb, and your LVM physical volume is on the first partition (which is still only 10GB). So you need to:
- Resize the partition to fill the disk
- Run
pvresize
to pick up the new size.
Personally, on Google Compute instances with LVM, I don't bother partitioning the disk — it serves no real purpose and makes resize much harder. I'd guess the same applies to Amazon. Just put the PV on the full block device (xvdb instead of xvdb1). Then you just have to run pvresize
.
To resize the partition, use your favorite partition table editor. You probably have to delete the partition and create a new one making sure the start sector stays the same. That is extremely important; being a single sector off means losing your data. Then partprobe or kpartx might be able to load the updated table into the kernel with it live, otherwise a reboot is required.
Another alternative is presumably just to attach a third virtual disk, and put another PV there. You can add it to the same volume group, and grow your LVs that way.
You've partitioned xvdb, and your LVM physical volume is on the first partition (which is still only 10GB). So you need to:
- Resize the partition to fill the disk
- Run
pvresize
to pick up the new size.
Personally, on Google Compute instances with LVM, I don't bother partitioning the disk — it serves no real purpose and makes resize much harder. I'd guess the same applies to Amazon. Just put the PV on the full block device (xvdb instead of xvdb1). Then you just have to run pvresize
.
To resize the partition, use your favorite partition table editor. You probably have to delete the partition and create a new one making sure the start sector stays the same. That is extremely important; being a single sector off means losing your data. Then partprobe or kpartx might be able to load the updated table into the kernel with it live, otherwise a reboot is required.
Another alternative is presumably just to attach a third virtual disk, and put another PV there. You can add it to the same volume group, and grow your LVs that way.
answered 10 hours ago
derobertderobert
75.4k8164223
75.4k8164223
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f512620%2fresize-ebs-with-lvm%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
-aws, lvm