Hello there,
When I attempted to create the initial ramdisk images it failed with
loopback devices are in use!
# mkinitrd /boot/initrd-2.4.9-34.img 2.4.9-34
All of your loopback devices are in use!
Any idea ?
Much thanks.
Regards,
Daniel
This e-mail message (and attachments) is confidential, and / or privileged and is intended for the use of the addressee only. If you are not the intended recipient of this e-mail you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality or privilege is not waived or lost by reason of mistaken delivery to you. DPWS is not responsible for any information not related to the business of DPWS. If you have received this e-mail in error please destroy the original and notify the sender.
For information on services offered by DPWS, please visit our website at http://www.dpws.nsw.gov.au
Hi,
On Tue, 23 Jul 2002, Daniel Lim wrote:
> # mkinitrd /boot/initrd-2.4.9-34.img 2.4.9-34
> All of your loopback devices are in use!
Yes, if all your loopback devices are in use, you'll have to umount some.
cat /proc/mounts, and there umount some of the filesystems with the loop
option.
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------
Hi,
Thanks for your prompt response.
The /proc/mounts does NOT show any loopback devices. I have however,
umounted 3 FS but it still failed with same messages??
Daniel
>>> Thunder from the hill <[email protected]> 23/07/2002 16:34:28
>>>
Hi,
On Tue, 23 Jul 2002, Daniel Lim wrote:
> # mkinitrd /boot/initrd-2.4.9-34.img 2.4.9-34
> All of your loopback devices are in use!
Yes, if all your loopback devices are in use, you'll have to umount
some.
cat /proc/mounts, and there umount some of the filesystems with the
loop
option.
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------
Hi,
On Tue, 23 Jul 2002, Daniel Lim wrote:
> The /proc/mounts does NOT show any loopback devices. I have however,
> umounted 3 FS but it still failed with same messages??
It was about umounting loop filesystems...
What do you have in /dev/loop (devfs), or what /dev/loopx devices (no
devfs, ls /dev/loop*) do you have?
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------
Hi,
On Tue, 23 Jul 2002, Daniel Lim wrote:
> brw-rw---- 1 root disk 7, 0 Jul 23 16:06 /dev/loop0
So no devfs. Is the loop module loaded? Do a cat /dev/loop15 to see, but
make sure that there is no mounted filesystem there. Please don't send the
result in any case. If you get "No such file", you'll need to modprobe
loop.
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------
Hi Thanks again,
I have this
# ls -l /dev/loop*
brw-rw---- 1 root disk 7, 0 Jul 23 16:06 /dev/loop0
brw-rw---- 1 root disk 7, 1 Jul 23 16:06 /dev/loop1
brw-rw---- 1 root disk 7, 10 Jul 23 16:06 /dev/loop10
brw-rw---- 1 root disk 7, 11 Jul 23 16:06 /dev/loop11
brw-rw---- 1 root disk 7, 12 Jul 23 16:06 /dev/loop12
brw-rw---- 1 root disk 7, 13 Jul 23 16:06 /dev/loop13
brw-rw---- 1 root disk 7, 14 Jul 23 16:06 /dev/loop14
brw-rw---- 1 root disk 7, 15 Jul 23 16:06 /dev/loop15
brw-rw---- 1 root disk 7, 2 Jul 23 16:06 /dev/loop2
brw-rw---- 1 root disk 7, 3 Jul 23 16:06 /dev/loop3
brw-rw---- 1 root disk 7, 4 Jul 23 16:06 /dev/loop4
brw-rw---- 1 root disk 7, 5 Jul 23 16:06 /dev/loop5
brw-rw---- 1 root disk 7, 6 Jul 23 16:06 /dev/loop6
brw-rw---- 1 root disk 7, 7 Jul 23 16:06 /dev/loop7
brw-rw---- 1 root disk 7, 8 Jul 23 16:06 /dev/loop8
brw-rw---- 1 root disk 7, 9 Jul 23 16:06 /dev/loop9
>>> Thunder from the hill <[email protected]> 23/07/2002 16:54:02
>>>
Hi,
On Tue, 23 Jul 2002, Daniel Lim wrote:
> The /proc/mounts does NOT show any loopback devices. I have however,
> umounted 3 FS but it still failed with same messages??
It was about umounting loop filesystems...
What do you have in /dev/loop (devfs), or what /dev/loopx devices (no
devfs, ls /dev/loop*) do you have?
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------
This e-mail message (and attachments) is confidential, and / or privileged and is intended for the use of the addressee only. If you are not the intended recipient of this e-mail you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality or privilege is not waived or lost by reason of mistaken delivery to you. DPWS is not responsible for any information not related to the business of DPWS. If you have received this e-mail in error please destroy the original and notify the sender.
For information on services offered by DPWS, please visit our website at http://www.dpws.nsw.gov.au
Reminds me that at least in 2.4.16 you have to expicitly release the loop
device after an unmount:
pcast2:/tmp # dd if=/dev/zero of=tst bs=1024 count=1440
1440+0 records in
1440+0 records out
pcast2:/tmp # mke2fs tst
mke2fs 1.26 (3-Feb-2002)
tst is not a block special device.
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
184 inodes, 1440 blocks
72 blocks (5.00%) reserved for the super user
First data block=1
1 block group
8192 blocks per group, 8192 fragments per group
184 inodes per group
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
pcast2:/tmp # mount -o loop /tmp/tst /mnt/tmp
pcast2:/tmp # umount /mnt/tmp
pcast2:/tmp # losetup -d /dev/loop0
pcast2:/tmp # losetup -d /dev/loop0
ioctl: LOOP_CLR_FD: No such device or address
pcast2:/tmp #
Note the two "losetup -d" commands above. The first one succeeds so umount
didn't release the loop device.
On Tue, 23 Jul 2002 00:34:28 -0600 (MDT) Thunder from the hill <[email protected]> wrote:
> Hi,
>
> On Tue, 23 Jul 2002, Daniel Lim wrote:
> > # mkinitrd /boot/initrd-2.4.9-34.img 2.4.9-34
> > All of your loopback devices are in use!
>
> Yes, if all your loopback devices are in use, you'll have to umount
> some.
> cat /proc/mounts, and there umount some of the filesystems with the loop
> option.
>
> Regards,
> Thunder
Hi,
On Tue, 23 Jul 2002, Daniel Lim wrote:
> /lib/modules/2.4.2-2/kernel/drivers/block/loop.o: unresolved symbol
> do_generic_file_read_R63b9dc6b
This is you're trying to use the correct module, but it's from the wrong
kernel version. BTW, yes, you might try losetup -d /dev/loopx (or even
better, when no loop devices are mounted,
for d in /dev/loop*; do
losetup -d $d
done)
BAW, what's your kernel (uname -r)?
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------
Hi,
My problem is fixed, it was for some reasons, due to corrupted or
imcompatible module for
/lib/modules/2.4.2-2/kernel/drivers/block/loop.o, I restored the module
and it all worked like charms.
Thanks for all your help.
Regards,
Daniel
>>> Thunder from the hill <[email protected]> 23/07/2002 18:25:04
>>>
Hi,
On Tue, 23 Jul 2002, Daniel Lim wrote:
> /lib/modules/2.4.2-2/kernel/drivers/block/loop.o: unresolved symbol
> do_generic_file_read_R63b9dc6b
This is you're trying to use the correct module, but it's from the
wrong
kernel version. BTW, yes, you might try losetup -d /dev/loopx (or even
better, when no loop devices are mounted,
for d in /dev/loop*; do
losetup -d $d
done)
BAW, what's your kernel (uname -r)?
Regards,
Thunder
--
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y-
------END GEEK CODE BLOCK------