From: Johannes Truschnigg <johannes@truschnigg.info>
To: Stefanie Leisestreichler <stefanie.leisestreichler@peter-speer.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 1 | Extending Logical Volume
Date: Sun, 12 Jan 2025 20:38:55 +0100 [thread overview]
Message-ID: <Z4QaT06f3Ieyy4wW@vault.lan> (raw)
In-Reply-To: <c8b2fb3b-80c5-464f-aaa7-0883d5689193@peter-speer.de>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
Hi Steffi,
On Sun, Jan 12, 2025 at 08:02:19PM +0100, Stefanie Leisestreichler wrote:
> Hi.
> I have the system layout shown below.
> Can I safely use
>
> lvextend -L +50GB /dev/mapper/vg_raid1-root
> and after that
> resize2fs /dev/mapper/vg_raid1-root
The snipped output below seems to suggest that there's two SATA disks that are
partitioned with one partition each. These partitions across devices form a
2-leg RAID1 array via md/mdadm.
That RAID1 array itself is in use as a Physival Volume for LVM2, and it hosts
a Volume Group with a Logical Volume at /dev/mapper/vg_raid1-root that you
want to resize.
> [...]
With these assumptions verified, the operation you are about to execute seems
perfectly safe to me. You can even make `lvresize` perform the fs resizing for
you, and shorten the whole ordeal to just
# lvresize --size +50GB --resizefs /dev/mapper/vg_raid1-root
Godspeed, and remember to always keep working backups handy regardless! ;)
--
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )
www: https://johannes.truschnigg.info/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-12 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 19:02 RAID 1 | Extending Logical Volume Stefanie Leisestreichler
2025-01-12 19:38 ` Johannes Truschnigg [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-03 11:53 Stefanie Leisestreichler (Febas)
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=Z4QaT06f3Ieyy4wW@vault.lan \
--to=johannes@truschnigg.info \
--cc=linux-raid@vger.kernel.org \
--cc=stefanie.leisestreichler@peter-speer.de \
/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;
as well as URLs for NNTP newsgroup(s).