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 Brian Sullivan <[EMAIL PROTECTED]> writes: > 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 the ISO files are good > and I am able to mount and umount each of them (once > mounted I am able to read and access all the files > contained in them) using the loop device. > > 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 is the max > number of processes for my user id. I confirmed this > by using the "ulimit -u" command to lower my process > limit. It appears the mount command is leaving > someting in some sort of process table in kernel > memory (nothing shows in ps or top or in /proc/#### as > being left behind). Has anybody any sort of experience > with this at all? Any suggestions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
