Loopback problems (Re: Where is losetup?)

Guentcho Skordev <[email protected]>
Newsgroups gmane.linux.tomsrtbt
Message-ID <[email protected]>
Hello,

On Mon, Oct 07, 2002 at 07:17:49PM +0200, [email protected] wrote:

> >     * Subject: Re: [tomsrtbt] Where is losetup?
> >     * From: Tom Oehser <[email protected]>
> >     * Date: Thu, 4 Oct 2001 20:57:58 -0400 (EDT)
> >
> >It is a documentation error and changelog error, it seems, since it is not
> >there.  Do you really need it, and why?  My inclination is to just put a
> >libc5 losetup on the add-ons sites.  Losetup is _not_ needed to make and
> >to use loop filesystems- only to make them encrypted or use an offset...
> 
> Exactly. I've only managed to make a copy of the whole hard disc just
> before it stopped to response. Unfortunately I don't have enough place
> to split the large file into partitions, that's why I needed losetup to
> be able to mount them.

Actually, I don't need losetup, because I have noticed that something I have
read somewhere else, works in tomsrtbt 2.0.103:

	mount -o loop,offset=xxxx ....

But loop isn't documented in the mount manual page.
Maybe there are also options for other things losetup can do?

There seems to exist a problem with loop in 2.0.103:
----------------------------------------------------
(/dev/hdb has FAT16)

 /# mount /dev/hdb1 /mnt
 VFS: Can't find an ext3 filesystem on dev ide0(3,65).

 /# mount -oloop /mnt/rescue/tom20103/raw/tom20103.raw /fl
 /# umount /fl

 /# umount /mnt
 umount: /dev/hdb1: device is busy
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
While rebooting:

 Trace/breakpoint trap
 Trace/breakpoint trap
 umount: /dev/hdb1: device is busy
 Please stand by while rebooting the system.

I have also noticed I can't mount and unmount the image more than 4 times
without creating new loop devices.

Regards
Guentcho
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.