Re: kpartx return codes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel



[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux