All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Ross Anderson <rosander@dsotm.net>
Subject: Re: kpartx fails 4k block partition
Date: Thu, 13 Mar 2014 11:01:32 +0000	[thread overview]
Message-ID: <5321900C.3030008@redhat.com> (raw)
In-Reply-To: <5320DDA1.3060309@dsotm.net>

On 03/12/2014 10:20 PM, Ross Anderson wrote:
> Under 0.50 multipath tools release, partitions are not being created for
> devices that are 4k Native.  This is under kernel 3.13.6, udev-208.
> 
> http://pastebin.com/Nnd4Ym4W

The devices below don't appear in your lsblk output so it's hard to say
whether the partitions kpartx prints for the devices are valid or not:

>     ##kpartx sfx4k
>     sfx4k1 : 0 2056 sfx4k 2048
>     sfx4k2 : 0 165068760 sfx4k 8192
>     ##kpartx samplelib
>     samplelib1 : 0 2056 samplelib 2048
>     samplelib2 : 0 1171863512 samplelib 8192

That said the tables above look perfectly plausible. It would help to
verify that if you could post the partition tables the devices contain
(preferably in sector units).

> kpartx -a 2 /dev/dm-2
> failed to stat() 2

What's that '2' doing there? The only thing kpartx expects following the
'-a' is the whole disk device:

    SYNOPSIS
       kpartx [-a | -d | -l] [-v] wholedisk

What happens when you run 'kpartx -a /dev/mapper/sfx4k? (or samplelib).

Regards,
Bryn.

  reply	other threads:[~2014-03-13 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 16:34 [PATCH 0/2] multipath: Stop extra scans on stacked devices Xose Vazquez Perez
2014-03-12 21:47 ` Christophe Varoqui
2014-03-12 22:20 ` kpartx fails 4k block partition Ross Anderson
2014-03-13 11:01   ` Bryn M. Reeves [this message]
2014-03-13 15:00     ` kpartx fails 4k block partition *changed** 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=5321900C.3030008@redhat.com \
    --to=bmr@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=rosander@dsotm.net \
    /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.