From: "Pádraig Brady" <pbrady@redhat.com>
To: dm-devel@redhat.com
Subject: Re: kpartx return codes
Date: Thu, 12 Jan 2012 17:58:29 +0000 [thread overview]
Message-ID: <4F0F1F45.5040208@redhat.com> (raw)
In-Reply-To: <4EDF8C5C.9080900@redhat.com>
On 12/07/2011 03:55 PM, Pádraig Brady wrote:
> I noticed some issues with kpartx return codes:
>
> On an unconnected loop device we get warnings,
> but an EXIT_SUCCESS ?
>
> # kpartx -a /dev/loop1 && echo EXIT_SUCCESS
> read error, sector 0
> llseek error
> llseek error
> llseek error
> EXIT_SUCCESS
>
> Also for a loop device that is connected,
> I get a "failed" warning, but the EXIT_SUCCESS
> is appropriate in that case as the mapped device
> is present and usable
>
> # kpartx -a /dev/loop0
> /dev/mapper/loop0p1: mknod for loop0p1 failed: File exists
>
> cheers,
> Pádraig.
>
> p.s. the git repo on kernel.org is no longer available
repo is still not available.
I was kinda waiting for that before attempting to look at the above issues.
cheers,
Pádraig.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2012-01-12 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 15:55 kpartx return codes Pádraig Brady
2012-01-12 17:58 ` Pádraig Brady [this message]
2012-01-12 18:58 ` Christophe Varoqui
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=4F0F1F45.5040208@redhat.com \
--to=pbrady@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.