From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] can't use LVM2 - "Failed to write physical volume"? [SOLVED]
Date: Thu, 10 Jan 2008 13:12:46 +0100 [thread overview]
Message-ID: <47860BBE.3090302@wpkg.org> (raw)
In-Reply-To: <4784F989.3030801@wpkg.org>
Tomasz Chmielewski schrieb:
> It seems to me that for some reason it's not possible to create a
> physical volume on a DRBD device. Below, we can see that running
> "pvcreate" succeeds and than fails, then it succeeds again etc.:
>
> # pvcreate -d -v /dev/drbd0
> Set up physical volume for "/dev/drbd0" with 976544952 available
> sectors
> Zeroing start of device /dev/drbd0
> Physical volume "/dev/drbd0" successfully created
>
> # pvcreate -d -v /dev/drbd0
> Wiping cache of LVM-capable devices
> Set up physical volume for "/dev/drbd0" with 976544952 available
> sectors
> Zeroing start of device /dev/drbd0
> Failed to write physical volume "/dev/drbd0"
Looks like LVM doesn't like some raw devices?
I added a partition to /dev/drbd0 with fdisk.
Then, I added a drive mapping with kpartx.
It works fine now.
# kpartx -a -v /dev/drbd0
add map drbd0p1 : 0 976543092 linear /dev/drbd0 63
# pvcreate -d -v /dev/mapper/drbd0p1
Set up physical volume for "/dev/mapper/drbd0p1" with 976542708
available sectors
Zeroing start of device /dev/mapper/drbd0p1
Physical volume "/dev/mapper/drbd0p1" successfully created
Anyway, why does it fail if I want to set up LVM on raw DRBD device? A
bug or a feature?
--
Tomasz Chmielewski
http://wpkg.org
prev parent reply other threads:[~2008-01-10 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 16:42 [linux-lvm] can't use LVM2 - "Failed to write physical volume"? Tomasz Chmielewski
2008-01-10 12:12 ` Tomasz Chmielewski [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=47860BBE.3090302@wpkg.org \
--to=mangoo@wpkg.org \
--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 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.