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.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
01-12-2012, 08:08 PM
Mikulas Patocka
kpartx -l side effects
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.
Mikulas--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
01-13-2012, 12:16 PM
Pádraig Brady
kpartx -l side effects
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.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
01-13-2012, 03:42 PM
Mikulas Patocka
kpartx -l side effects
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--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
01-13-2012, 05:54 PM
Pádraig Brady
kpartx -l side effects
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
kpartx -l side effects
