From: "Pádraig Brady" <pbrady@redhat.com>
To: christophe.varoqui@opensvc.com
Cc: dm-devel@redhat.com
Subject: Re: kpartx -l side effects
Date: Fri, 13 Jan 2012 18:54:10 +0000 [thread overview]
Message-ID: <4F107DD2.4050402@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1201131142170.32458@hs20-bc2-1.build.redhat.com>
On 01/13/2012 04:42 PM, Mikulas Patocka wrote:
>
>
> On Fri, 13 Jan 2012, Pádraig Brady wrote:
>
>> On 01/12/2012 09:08 PM, Mikulas Patocka wrote:
>>>
>>>
>>> On Thu, 12 Jan 2012, Pádraig Brady wrote:
>>>
>>>> I was playing around with kpartx on 2.6.40.4-5.fc15.x86_64 and did:
>>>> kpartx -l /bin/ls
>>>> Now I get "text file busy" when trying to run ls.
>>>> How does one undo that?
>>>>
>>>> cheers,
>>>> Pádraig.
>>>
>>> Run losetup -a, you find that one of loopback devices is assigned to
>>> /bin/ls (for example /dev/loop0). Then, run losetup -d /dev/loop0 to
>>> remove that block device. Then, you can use /bin/ls again.
>>
>> Cool that works.
>> It's still a bug though right?
>> I.E. `kpartx -l` has side effects (only when it can't map partitions).
>>
>> cheers,
>> Pádraig.
>
> It may be a bug. You can report it to kpartx developers.
>
> Mikulas
Sorry, http://christophe.varoqui.free.fr/ pointed here.
I've copied Christophe directly.
thanks,
Pádraig.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2012-01-13 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 18:02 kpartx -l side effects Pádraig Brady
2012-01-12 21:08 ` Mikulas Patocka
2012-01-13 13:16 ` Pádraig Brady
2012-01-13 16:42 ` Mikulas Patocka
2012-01-13 18:54 ` Pádraig Brady [this message]
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=4F107DD2.4050402@redhat.com \
--to=pbrady@redhat.com \
--cc=christophe.varoqui@opensvc.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 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).