From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: partx fails 4096 block size
Date: Tue, 16 Sep 2014 09:52:34 +0100 [thread overview]
Message-ID: <20140916085234.GA21419@localhost.localdomain> (raw)
In-Reply-To: <54174287.30508@dsotm.net>
On Mon, Sep 15, 2014 at 02:48:23PM -0500, Ross Anderson wrote:
> I'd appreciate any help in troubleshooting this. Quiet frustrating not being
> able to use mpath on 4k blocks.
Doesn't seem related to sector size.
> http://pastebin.com/EbTMXdvE
> ###partx -a-v
> partition: none, disk: /dev/dm-0, lower: 0, upper: 0
> /dev/dm-0: partition table type 'gpt' detected
> partx: /dev/dm-0: adding partition #1 failed: Invalid argument
partx is trying to call a BLKPG partition management ioctl on a
device-mapper device. Since dm devices are not partitionable it
fails with EINVAL.
> partx: /dev/dm-0: adding partition #2 failed: Invalid argument
> partx: /dev/dm-0: error adding partitions 1-2
The partx program comes from the util-linux package:
$ qwhich partx
util-linux-2.24.2-1.fc20.x86_64
You're probably looking for kpartx which is part of multipath-tools. On
Red Hat distros it's in a separate sub-package named kpartx:
$ qwhich kpartx
kpartx-0.4.9-56.fc20.x86_64
The kpartx command reads partition data from the disk and creates
device-mapper linear maps corresponding to each discovered partition.
This allows you to access the partitions on a device-mapper device as
separate dm devices (e.g. you'd get devices with paths like
'/dev/mapper/dm-0p1' or whatever depending on the -p switch given).
Most distros today will automatically run kpartx when new multipath
devices appear or when they change so you shouldn't need to run it
manually all the time.
Regards,
Bryn.
next prev parent reply other threads:[~2014-09-16 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 19:48 partx fails 4096 block size Ross Anderson
2014-09-16 8:52 ` Bryn M. Reeves [this message]
2014-09-16 15:35 ` Ross Anderson
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=20140916085234.GA21419@localhost.localdomain \
--to=bmr@redhat.com \
--cc=dm-devel@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.