From: "Frédéric Baldit" <frederic.baldit@free.fr>
To: linux-lvm@lists.linux.dev
Subject: is it possible to use LVM AFTER system installation?
Date: Sat, 21 Feb 2026 18:58:16 +0100 [thread overview]
Message-ID: <20260221185816.34fab009@ThinkPadT15g.lan> (raw)
Hi everybody,
I'm a debian 12 user, running it on a system which was initially
installed without LVM (on a thinkpad laptop)n with classical netinst. My
system is totally installed on a unique nvme disk, with distinct
partitions, among which a /home partition for all my personal data.
I recently installed a second nvme disk (512G capacity). I would like
to extend my /home ext4 partition (which is now exclusively on
/dev/nvme0n1p6, 436G) so that I can keep my old data but have
the possibility to split /home on the initial disk and the second
recently added disk.
This seems to be possible with LVM but only when decided at the
beginning of the installation. Right or wrong?
Or would it possible to:
0) install lvm2 on my system
1) create a new ext4 partition (512G size) on the new nvme disk (using
all available space, 512G, on it)
2) create a new PV with this partition
3) create a new VG containing this unique PV
4) create a new LV on this VG
5) format this LV as an ext4 filesystem with mkfs.ext4
6) mount this LV on a new system directory, say /home1
7) migrate all the data on my old /home to the new /home1
8) modify the VG created before in order to add to it the
/dev/nvme0n1p6 PV
9) resize the LV so that it can use the new PV added
10) rename /home1 to /home
Is this globally correct??? Step 7 if crucial, as I really don't want
any loss or corruption of personal data during the transfer.
Thank's in advance for any help to my two questions,
F. Baldit.
--
Frédéric Baldit
next reply other threads:[~2026-02-21 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 17:58 Frédéric Baldit [this message]
2026-02-21 18:35 ` is it possible to use LVM AFTER system installation? Roger Heflin
2026-02-21 20:20 ` Christian Recktenwald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260221185816.34fab009@ThinkPadT15g.lan \
--to=frederic.baldit@free.fr \
--cc=linux-lvm@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox