From: Jakob Oestergaard <jakob@unthought.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dm-mirror/kmirrord oops
Date: Mon, 27 Jun 2005 13:57:16 +0200 [thread overview]
Message-ID: <20050627115716.GH422@unthought.net> (raw)
In-Reply-To: <20050627070709.GA9169@adren.mine.nu>
On Mon, Jun 27, 2005 at 09:07:09AM +0200, Cyril Chaboisseau wrote:
> I just had a big problem lately when I wanted to migrate my PV from one
> disk to another
>
> to do so, I first created a LVM partition on my second disk,
>
> then I initialized the partition (pvcreate)
> # pvcreate /dev/sdb1
>
> I extended my vg to the newly PV
> # vgextend vg /dev/sdb1
>
> and then I tried to move the data from the old PV to the newly created
> # pvmove -v /dev/sda4 /dev/sdb1
>
> everything went fine for maybe half an hour, but at 21% it froze
Is your root filesystem mounted on an LV in 'vg' ?
As far as I know, this is a known problem - you cannot pvmove your root
filesystem.
But on another note; you should not have your root (or at least /etc)
filesystem on LVM - because the LVM backup/recovery files are written
there, and if LVM screws up completely, you'll then have no way of
recovering (since the recovery files you need to get LVM going are
stored via. LVM).
I always create a partition for / and keep /boot, /sbin, /lib and /etc
there.
Then, I create another partition and make it a PV, put /var, /usr and
everything else on LVM.
That way I can pvmove anything without running into the bug you
(probably) saw, and I will be able to recover the LVM in case it screws
up (which I haven't seen yet).
--
/ jakob
next prev parent reply other threads:[~2005-06-27 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 7:07 dm-mirror/kmirrord oops Cyril Chaboisseau
2005-06-27 11:57 ` Jakob Oestergaard [this message]
2005-06-27 15:43 ` Cyril Chaboisseau
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=20050627115716.GH422@unthought.net \
--to=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.