Thank you all for your responses relative to full file system on
Alpha/Unix 4.0E.
As many of you suspected, the /tmp directory was full (so was /).
When we cleaned up root and mounted /tmp to a different drive, it all
worked.
These are the answers (8 ans.):
Special Thanks to:
Anthony A. D
Steve VanDenver
Dr. Tom Blinn
Wolfram Klaus
Ian Mortimer
Dan Riley
Olle Eriksson
Pat Lampert
Answers
1-Look at all the filesystems, including /tmp.
2-You may be reaching the filesystem's inode limit; there is a limit on
the total number of files that a filesystem can hold, as well as a limit
on the total space available.
You can check how many files (inodes) are available with "df -i".
3-Only a guess, but it sounds almost like the "ar" program has a 32-bit
limit on the size of an archive.
I can't find an explicit statement to that effect in the "ar" man page
(or the man 4 ar page for the file format), but it does say that:
When ar creates an archive, it creates administrative information in a
for-
mat that is portable across all machines.
and when I see a statement like that, I think "lots of machines don't
support
64-bit data in any clean way".
4-Which file system is full (probably "/")?
This is usually caused by the archiver (ar) filling up /tmp, which lives
in the /-file system by default. Thus, if your root file system is
pretty full, you are likely to sees these errormessages when building
large libraries. To get around this you should set the environment
variable TMPDIR to /var/tmp or something else or use the -l flag of
ar.
5-ar builds the archive in /tmp before moving it into place.
You need more space in /tmp.
(I'm not sure if ar recognizes the TMPDIR environment variable.
You could try setting TMPDIR to a filesystem with more free space
and see if that solves the problem.)
6-Most likely, /tmp is filling up. Increase the size of /tmp, or use
the TMPDIR environment variable to tell ar to use a different disk
for scratch space.
7-This is because ar uses temporary space in /tmp and your
/tmp area fills up during the ar session
8-I'm don't know if you have received an answer from this mailing list
already, but if you need assistance and you reside in the U.S. you can
call
(800)354-9000 and ask for help with Tru64 UNIX software development.
There
are phone numbers for support in other countries listed off the
http://www.compaq.com/support web page.
Just to give a one time shot at this I suspect your problem is caused by
shell limits. 2mb is the default stack size for the shell on Tru64 UNIX.
For
csh try doing an unlimit command, for ksh try ulimit -s 32768.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
Received on Wed Sep 20 2000 - 17:59:20 NZST