* kpartx return codes
@ 2011-12-07 15:55 Pádraig Brady
2012-01-12 17:58 ` Pádraig Brady
0 siblings, 1 reply; 3+ messages in thread
From: Pádraig Brady @ 2011-12-07 15:55 UTC (permalink / raw)
To: dm-devel
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
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kpartx return codes
2011-12-07 15:55 kpartx return codes Pádraig Brady
@ 2012-01-12 17:58 ` Pádraig Brady
2012-01-12 18:58 ` Christophe Varoqui
0 siblings, 1 reply; 3+ messages in thread
From: Pádraig Brady @ 2012-01-12 17:58 UTC (permalink / raw)
To: dm-devel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kpartx return codes
2012-01-12 17:58 ` Pádraig Brady
@ 2012-01-12 18:58 ` Christophe Varoqui
0 siblings, 0 replies; 3+ messages in thread
From: Christophe Varoqui @ 2012-01-12 18:58 UTC (permalink / raw)
To: device-mapper development
On jeu., 2012-01-12 at 17:58 +0000, Pádraig Brady wrote:
> 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.
>
The master repo of multipath-tools is now on http://git.opensvc.com
Sorry for not advertizing more.
cvaroqui
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-01-12 18:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-07 15:55 kpartx return codes Pádraig Brady
2012-01-12 17:58 ` Pádraig Brady
2012-01-12 18:58 ` Christophe Varoqui
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).