Sponsored Content
Full Discussion: Error Message
Top Forums UNIX for Dummies Questions & Answers Error Message Post 28780 by RTM on Tuesday 24th of September 2002 11:53:27 AM
Old 09-24-2002
Your Veritas file system for /tmp is full - no more space left. This could possibly (probably) hang your system unless you fix it.

If you are not the administrator - then contact that person.
If you are the admin - well, it looks like you have some learning to do since you didn't know about vxfs and a full file system.

Some links that could possibly help -

Veritas Support (click on the knowledge base search).

Post what OS and version you are running (along with Veritas version) and maybe someone can give more info.

Check with your boss - see if you have a contract with your vendor or Veritas.

Since it's /tmp that is full, you can cd /tmp and see if there is anything you could possibly delete (rm). Try ls -ltcar to list the files in /tmp from oldest to newest. You may have a core file or a temporary file someone is using to build a report...
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

error message

Hi All, occasionally my server gives this error messages "NOTICE:HTFS Out of inodes on HTFS dev hd (1/42)" why ?? Alice. (3 Replies)
Discussion started by: alisev
3 Replies

2. UNIX for Advanced & Expert Users

Error message

I'm getting an error - symbol referencing errors. No output written to, etc Can anybody tell me why this is? (2 Replies)
Discussion started by: Dan Rooney
2 Replies

3. Solaris

Error message

Hi, My Solaris 5.8 system keeps getting this error at boot - "Can't set vol root to /vol" then /usr/sbin/vold: can't set vol root to /vol: Resource temporarily unavailiable Any idea what is wrong, and how do I fix it? (0 Replies)
Discussion started by: ghuber
0 Replies

4. UNIX for Advanced & Expert Users

Error message

Hi, My Solaris 5.8 system keeps getting this error at boot - "Can't set vol root to /vol" then /usr/sbin/vold: can't set vol root to /vol: Resource temporarily unavailiable Any idea what is wrong, and how do I fix it? (1 Reply)
Discussion started by: ghuber
1 Replies

5. UNIX for Dummies Questions & Answers

getting last error message

Question for unix programmers - what function I need to used to get the exact error message when the library failed to load? Thanks (1 Reply)
Discussion started by: tttttt
1 Replies

6. Shell Programming and Scripting

Error message

I am new to scripting. I am using the following script . BART.dat contains the string 'Y' . #!/bin/ksh cd /work/TCI/data_out file=`cat BART.dat` echo "$file" if ; then echo "true" fi When i am executing the above script i am getting the following error ./s.ksh: : not found ... (2 Replies)
Discussion started by: ammu
2 Replies

7. UNIX for Dummies Questions & Answers

Error Message

What does this means? - ERROR OPENING FILE - KEY LENGHT MISMATCH (2 Replies)
Discussion started by: RDM00
2 Replies

8. UNIX for Dummies Questions & Answers

Error Message

I keep getting an error message in a script im writing, this line is allways pointed out. if and this is the message i keep getting. line 32: [: 8: unary operator expected Whats wrong with it? Please Help. (5 Replies)
Discussion started by: chapmana
5 Replies

9. UNIX for Dummies Questions & Answers

What does this Error Message Mean

Hi I found the following error message in my logs: warning: /etc/hosts.deny, line 6: can't verify hostname: getaddrinfo(localhost) didn't return ::ffff:222.255.28.33 What is the error message trying to indicate? That there is a problem with line 6 (2 Replies)
Discussion started by: mojoman
2 Replies
vxiod(1M)																 vxiod(1M)

NAME
vxiod - start, stop, and report on Veritas Volume Manager I/O threads SYNOPSIS
vxiod vxiod [-f ] [set count] DESCRIPTION
The vxiod utility starts, stops, or reports on Veritas Volume Manager (VxVM) I/O kernel threads. An I/O thread provides a process context for performing I/O in VxVM. When the vxio module is loaded, 16 I/O threads are created, plus 2 threads per additional CPU for a system with more than 8 CPUs, up to a maximum of 64 threads. At least one I/O thread must be running while the vxio module is loaded, and the number of I/O threads cannot be forced to zero. When invoked with no arguments, vxiod prints the current number of I/O threads to the standard output. The number of threads that is required for handling I/O requests depends on the system load and usage. If volume recovery seems to proceed more slowly at times, it may be possible to improve its performance by increasing the number of I/O threads up to a maximum of 64. KEYWORDS
set When invoked with the set keyword, vxiod creates the number of I/O threads specified by count. If more volume I/O threads exist than are specified by count, the excess processes terminate. If more than the maximum number(64) are specified, the requested number is silently truncated to that maximum. OPTIONS
-f This option has no effect from release 5.0 onward. The number of I/O threads cannot be reduced to zero. EXIT CODES
The vxiod utility prints a diagnostic on the standard error, and exits if an error is encountered. If an I/O request occurs within a I/O thread, the state of that I/O request is not reflected in the exit status for vxiod. Otherwise, vxiod returns a non-zero exit status on error. Usage errors result in an exit status of 1 and a usage message. If the requested number of threads cannot be created, the exit status is 2, and the number of threads that were successfully started is reported. If any other error occurs, the exit status is 3. FILES
/dev/vx/iod The device used to report on and start volume I/O threads. NOTES
Veritas Volume Manager I/O threads cannot be killed directly through the use of signals. Depending on the operating system, VxVM I/O threads may not appear in the list of processes that is output by the ps command. The number of I/O threads that is currently running can be determined by running vxiod. SEE ALSO
fork(2), ps(1), vxconfigd(1M), vxdctl(1M), vxintro(1M), vxio(7), vxiod(7) VxVM 5.0.31.1 24 Mar 2008 vxiod(1M)
All times are GMT -4. The time now is 09:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy