Bug 29908 - "losetup -d /dev/loop0" does not work.
Summary: "losetup -d /dev/loop0" does not work.
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
high
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-27 23:02 UTC by Need Real Name
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-28 16:55:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Need Real Name 2001-02-27 23:02:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.14-5.0 i686)


"losetup -d /dev/loop0" does not work.


Reproducible: Always
Steps to Reproduce:
1.Log on as root.
2."umount /mnt/cdrom"
3."losetup -d /dev/loop0"
	

Actual Results:  After step 2., the system reports that I had nothing
mounted.
After step 3., the system issues one message only: "Segmentation fault",
after which the system hangs.

Expected Results:  Step 3 should have reported that there was no loopback
device setup, or something like that. I should have been able to continue
without rebooting the system.

I was trying to set up a loopback CD device so that I could install our
BRU-Pro product and test it on Wolverine. 
After rebooting the system, I was able to continue successfully by just
skipping the "umount /mnt/cdrom" and "losetup -d /dev/loop0" commands. I
simply issued the following commands:

    losetup /dev/loop0 /tmp/brupro_1.0.2.0.iso
    mount /dev/loop0 /mnt/cdrom
    cd /mnt/cdrom

This was successful, and I was able to install our BRU-Pro product and
continue testing.

Comment 1 Arjan van de Ven 2001-02-28 08:50:35 UTC
Does the kernel give an oops ?

Comment 2 Arjan van de Ven 2001-02-28 15:09:05 UTC
Ok. I can reproduce this.... Investigating

Comment 3 Need Real Name 2001-02-28 16:53:12 UTC
The only reason I reported this under "kernel" is that bugzilla didn't give me
an entry under "losetup".

Comment 4 Arjan van de Ven 2001-02-28 16:55:39 UTC
It's a kernel bug al right...

Comment 5 Arjan van de Ven 2001-02-28 18:34:01 UTC
Our next kernel build will have a fix for this. Please reopen this bug
if a kernel 2.4.2-0.1.17 or later (when it becomes available) does not fix this
for you.


Note You need to log in before you can comment on or make changes to this bug.