On Thu, 21 Jun 2001 11:00:35 -0500 (Central Daylight Time), Mark Bixby
<[log in to unmask]> wrote:

>Kurt Sager wrote:
>>
>> In one of our batch jobs, we execute in a shell many Posix commands:
>> Sometimes it doesn't work, aborting at ANY command with
>> a "cannot fork" message as shown below:
>>
>>  :run sh.hpbin.sys; info="-L"
>>
>>  /etc/profile 93: tabs: cannot fork: Resource busy, try again
>>  /etc/profile 93: tabs: Internal error: j_close: no processes
>>
>> What kind of resource might be busy?
>> how can we check what is the cause ?
>
>The most common cause of fork failing with resource busy is a lack of
>sufficient contiguous free disk space.
>--

... that must be available on ALL drives in the system volume set
ssimultaneously. You might have enough contig space availabe on LDEV 1,
but if not also on the other drives, mpe/posix (and thus you also) has
a problem. Well, most of the time anyway.

Check with a discfree a. If you have less then say 50 contig blocks of
at least size 1000 on any drive (in system vol), that's it. YMMV
though.
Danny A. van Delft   [log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *