HP3000-L Archives

March 2001, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Thu, 29 Mar 2001 09:59:08 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
Mark Bixby wrote:
>
> Try the following, courtesy of a Google web search on "contigvol":
>
> http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xe1f2f841489fd4118fef0090279cd0f9,00.html
> http://www.docs.hp.com/cgi-bin/doc3k/B3021690189.13992/44
>
> I'll let the CSY learning products manager know that contigvol never made it
> into the volume management manual.

But that might not be the ultimate solution.  At least with the original
fork() of death, the contiguous space had to reside on the same physical
volume as the parent.  This may have been "fixed" when they backed out
the optimized fork() routine that clones the parent's data structure,
but initially it had to be the same physical volume.  So the culprit
could be anything in MPEXL_SYSTEM_VOLUME_SET.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2