kam@titan.tsd.arlut.utexas.edu (Katherine Minister Hosch) (09/30/89)
Hi all. Thanks for all the responses in regard to my repeated watchdog
resets. The machine that was doing that has started exhibiting other
forms of alsheimers', and so is going to get a complete overhaul.
I've got another problem, stranger than that, I think. I am compiling ada
programs on a diskless 3/50, served by a 3/280 which has allocated 16 MB
of swap space to the 3/50. The 3/50 has just 4 MB of main memory. Upon
running a verdix ada debug session in one window, and compiling an ada
package in another, I got the following error:
Verdix Ada Compiler, Copyright 1984, 1985, 1986, 1987
Version 5.5 - Sun UNIX
Thu Mar 23 20:10:51 PST 1989 Sun 3 SunOS 4.0 (t)
File: /home/titan/kam/fsats/test.a
compiled Fri Sep 29 13:41:02 1989
by user kam
floating point processor SOFTWARE
current soft limit: 251658240; hard limit: 251658240
/home/titan/kam/fsats/test.a, line 11, char 15:fatal: Operating system denied v\irtual memory expansion to 6420479
Ada command finished at Fri Sep 29 13:41:07
Has anyone ever seen/heard of running out of virtual memory? The program
in the debug window is 319488 KB, and the program being compiled is itself
just 6545 bytes (but includes some standard and additional packages --
maybe another 100K.) Any ideas?
Katherine Minister Hosch: kam@titan.tsd.arlut.utexas.edu
Applied Research Laboratories (512)-835-3148
University of Texas at Austin
P.O. Box 8029, Austin, TX 78713-8029poffen@sj.ate.slb.com (Russ Poffenberger) (10/05/89)
In article <1901@brazos.Rice.edu> kam@titan.tsd.arlut.utexas.edu (Katherine Minister Hosch) writes: >X-Sun-Spots-Digest: Volume 8, Issue 150, message 14 of 15 > ...stuff deleted > >Has anyone ever seen/heard of running out of virtual memory? The program >in the debug window is 319488 KB, and the program being compiled is itself >just 6545 bytes (but includes some standard and additional packages -- >maybe another 100K.) Any ideas? > Yeah, increase your swap. 16 Mb is not much when you run suntools and possibly some other things. To check your current swap utilization, do pstat -T If you are at all close, then that is your problem. Once you run out of swap, thats it, you can't get memory anywhere else. Russ Poffenberger DOMAIN: poffen@sj.ate.slb.com Schlumberger Technologies UUCP: {uunet,decwrl,amdahl}!sjsca4!poffen 1601 Technology Drive CIS: 72401,276 San Jose, Ca. 95110 (408)437-5254
scott@uunet.uu.net (Scott Reed) (10/05/89)
kam@titan.tsd.arlut.utexas.edu (Katherine Minister Hosch) writes: >... >/home/titan/kam/fsats/test.a, line 11, char 15:fatal: Operating system denied v\irtual memory expansion to 6420479 >... >Has anyone ever seen/heard of running out of virtual memory? ... I think you can run out of virtual memory when your swap space is depleted. I've been having my swap space gobbled up by perfmeters and calentool when they're left running for a day or two. I'm no SunOS expert and haven't a clue why this happens. Noone else has been able to tell me why either. When I run out of memory, I run "top" to see who's using it up.
jdp@uunet.uu.net (John D. Polstra) (10/07/89)
In article <1901@brazos.Rice.edu> kam@titan.tsd.arlut.utexas.edu (Katherine Minister Hosch) writes: >X-Sun-Spots-Digest: Volume 8, Issue 150, message 14 of 15 > . . . >current soft limit: 251658240; hard limit: 251658240 > >/home/titan/kam/fsats/test.a, line 11, char 15:fatal: Operating system denied v\irtual memory expansion to 6420479 > >Ada command finished at Fri Sep 29 13:41:07 > >Has anyone ever seen/heard of running out of virtual memory? I've seen related questions a couple of times recently. Remember: the amount of virtual memory that a process can allocate is limited by the amount of swap space that is available on disk. The total amount of virtual memory allocated to all processes can never exceed the size of the swap region. You can get a good idea of the amount of virtual memory available by executing the command "/usr/etc/pstat -s". I just tried it, and it printed out: 5008k allocated + 1792k reserved = 6800k used, 44248k available A simple test program then succeeded in allocating 43 Mbytes of memory, but failed when it tried for 44 Mbytes. So the "available" figure is very close to the amount of virtual memory that can be allocated. If you want to increase this number, you will have to repartition your disk with a larger swap region, or add a second swap region using SWAPON(8). John Polstra jdp@polstra.UUCP Polstra & Co., Inc. ...{uunet,sun}!practic!polstra!jdp Seattle, WA (206) 932-6482