From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Fwd: file-based locking initialization failed after pvresize
Date: Fri, 31 May 2013 17:42:36 +0200 [thread overview]
Message-ID: <51A8C4EC.1010706@redhat.com> (raw)
In-Reply-To: <FFA8D6D8-8C13-41AF-8AAD-A42E9999BD6A@oxeva.fr>
Dne 31.5.2013 11:04, Gabriel Barazer napsal(a):
> Hi,
>
> Did you try booting off another system (e.g. live usb ) and restoring the LVM
> meta data ? If your root filesystem is still bootable, you can find a backup
> of the LVM metadata in /etc/lvm/backup, and then start over your data resizing
> procedure. Look for the vgcfgrestore command.
>
> The right procedure to resize a LV after growing a PV is :
> - adjust the partition table on sdb with fdisk, the simple way is deleting the
> partition table and creating a new one with the main partition having the same
> start offset (_very_ important)
> - THEN pvresize the device (no need to add any --setphysicalwhatever argument)
> - then lvresize, but if you want to be safe always check that the size you set
> is larger than the current volume size otherwise you can damage your data
> pretty bad. A good way to do this is to add a "+" in the lvresize command :
> lvresize -L +100G /device adds 100G to volume.
> - then run a filesystem resize command, depending on the filesystem used
> (xfs_growfs for XFS, resize2fs for ext4)
For couple years lvresize has the option '-r' so it knows how to resize
common filesystems (via fsadm script) - so it keeps the right order of
commands (very important in case you are reducing size)
Zdenek
next prev parent reply other threads:[~2013-05-31 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 18:48 [linux-lvm] file-based locking initialization failed after pvresize Christian Lahti
2013-05-30 21:02 ` Christian Lahti
[not found] ` <1369952053.99499.YahooMailClassic@web181504.mail.ne1.yahoo.com>
[not found] ` <CAEh524ZjZRizYoEimXg0OsLxz2kD8HLu2bqw2V2RbjYKdggVxw@mail.gmail.com>
2013-05-31 3:37 ` [linux-lvm] Fwd: " Christian Lahti
2013-05-31 8:23 ` Zdenek Kabelac
2013-05-31 9:04 ` Gabriel Barazer
2013-05-31 15:42 ` Zdenek Kabelac [this message]
[not found] ` <CAKPhfZMihQUFpeG=Tv_8pLwedw4Ugbf9u0jUP=5PTXfbUQHVaQ@mail.gmail.com>
[not found] ` <CAKPhfZMctTqczVBVxzdqL__=uYsOCKzkKD1dLj1zj4Z_0ZoW0g@mail.gmail.com>
[not found] ` <CAKPhfZPiD3Dux_Z_DGpNz0hyi1sJTXexwbstPe=WdjMGGh4Hog@mail.gmail.com>
2013-05-31 11:45 ` [linux-lvm] " service hofman
2013-05-31 17:20 ` Christian Lahti
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=51A8C4EC.1010706@redhat.com \
--to=zkabelac@redhat.com \
--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).