This problem isn't related to cdrecord or mkisofs but
since the users of both are familiar with ISO files I
thought maybe somebody would be able to help.
I am using Red Hat 7.3 and Red Hat 8.0 with the latest
patches on several servers and have created a variety
of ISO files using mkisofs. All
Hi,
If you create your loop devices manually
with losetup opposed to using mount -o loop, or if
you create your loop devices via mount -o loop
but /etc/mtab is a symlink to /proc/mounts,
then you have to delete the loop devices manually
using losetp -d /dev/loopX.
Hope this helps, Matthias
My /etc/mtab is a real file, not a link. I am doing
the mount by specifying the loop option in the
/etc/fstab file. Here is my fstab line:
/opt/insiteone/jbsim/sim0/reader01 /mnt/cdsim1
iso9660 noauto,loop,users 0 0
So I shouldn't have to worry about calling the
losetup -d. I did try adding
Ok, so you are doing it the right way.
I just browsed the kernel sources. losetup starts for each loop device
a kernel thread loop_thread. I assume this is the point of failure.
These kernel threads certainly should get be killed by losetup -d. I
suppose in your setup they aren't, either
On Tue, 28 Jan 2003, Brian Sullivan wrote:
The problem I am experiencing is that after a certain number of mounts I
get the error message fork: Resource temporarily unavailable on the
command line.
After much trouble shooting I realized that number of mounts/umount
sequences I am limited to
5 matches
Mail list logo
