From: Andy Smith <andy@strugglers.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Is it considered safe to resize a mounted partition (root filesystem) with lvextend
Date: Thu, 10 Nov 2016 11:22:40 +0000 [thread overview]
Message-ID: <20161110112240.GM21587@bitfolk.com> (raw)
In-Reply-To: <CAGXs5wWNcNf0mSW5bwYhc_xXyRcpmrJOD2m4Gg5wjS-EBvmMYw@mail.gmail.com>
Hi Kevin,
On Thu, Nov 10, 2016 at 09:12:58AM +0200, Kevin Wilson wrote:
> Is it safe to extend a mounted partition ?
Yes, if the tool you would use without LVM (e.g. resize2fs) is safe
for that. LVM just uses the appropriate tool, in your case
resize2fs, which can handle on-line resize.
> If I try it I get:
> "on-line resizing required" message, which I am not sure what it means.
It means that resize2fs has detected that the device is mounted and
so is doing an on-line resize. It is merely informational. That
message comes from resize2fs and so this is not really an LVM
question.
As you can see…
> lvextend --size +20G --resizefs /dev/mapper/vg_paeiserver5-lv_my_partition
> Extending logical volume lv_ubuntu to 34.00 GiB
> Logical volume lv_ubuntu successfully resized
…from this point on the output comes from the resize2fs program.
> resize2fs 1.42.9 (4-Feb-2014)
> Filesystem at /dev/mapper/vg_paeiserver5-lv_my_partition is mounted on
> /; on-line resizing required
> old_desc_blocks = 1, new_desc_blocks = 3
> The filesystem on /dev/mapper/vg_paeiserver5-lv_my_partition is now
> 8912896 blocks long.
Cheers,
Andy
prev parent reply other threads:[~2016-11-10 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 7:12 [linux-lvm] Is it considered safe to resize a mounted partition (root filesystem) with lvextend Kevin Wilson
2016-11-10 11:22 ` Andy Smith [this message]
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=20161110112240.GM21587@bitfolk.com \
--to=andy@strugglers.net \
--cc=linux-lvm@redhat.com \
/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).