10-25-2010
Either delete things, compress things, or move things somewhere else. And none of these unless you're sure the files in question are safe to do so. There's nothing mysterious about it, really.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I noticed that whenever something is printed from my workstation, the available disk space in the /dev/dsk/c0t0d0s0 decreases considerably. Hence, after using my workstation for sometime, I encounter an error message: "Filesystem Full" that prevents me from printing any further.
Is there a way to... (16 Replies)
Discussion started by: ilak1008
16 Replies
2. UNIX for Dummies Questions & Answers
I am running AIX 3 4.
When I do a df I get:
Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 32768 10232 69% 1309 16% /
/dev/hd2 917504 86360 91% 19744 18% /usr
/dev/hd9var 131072 67712 49% 617 ... (11 Replies)
Discussion started by: szodiac
11 Replies
3. HP-UX
Dear all,
What should I do with the following error message:
vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
Thanks for your advises, (1 Reply)
Discussion started by: hungevntelecom
1 Replies
4. Solaris
Good morning, sir!
I've a problem with FileSystem, the problem is FileSystem is full
First time, I've already read carefully the sticky thread
FileSystem full - What to lock for
https://www.unix.com/sun-solaris/25840-filesystem-full-what-look.html
And then, I will post some information of... (4 Replies)
Discussion started by: trantuananh24hg
4 Replies
5. UNIX for Dummies Questions & Answers
my root filesystem is eventually full "/dev/rdsk/c1d0s0" as a result i cannot boot to the operating system, i booted into the fail safe mode to check the space using df -h command i discover that it is eventually full. Also to my amazement i found that i cannot see the filesystem which mounted on... (1 Reply)
Discussion started by: seyiisq
1 Replies
6. Red Hat
Hi All,
How do I increase the root filesystem? It's getting full.
/ 90%
Here's the break down, below
232 dev
5624 tmp
*6764 bin
16860 root
*19680 sbin
*20436 lib64
28329 boot
*47992 etc
150012 var
*254540 lib
651708 home
*2445044 usr (5 Replies)
Discussion started by: itik
5 Replies
7. UNIX for Dummies Questions & Answers
Hello everybody, a very basic question.
Inspite of me deleting huge files in a filesystem(AIX 5.3) in oracle folder, the filesystem when i check using df -k still shows 100% full. Does that mean there is a process still pointing to the files which i deleted. how do i work around this.
Thanks!... (3 Replies)
Discussion started by: karthikosu
3 Replies
8. AIX
we are using aix 5.3 and we notice that the filesystem /usr is almost full. we have an oracle database running on the server.what are the cause why this filesystem is almost full.what should we do to free some space on this filesystem beside increase the size?thanks (4 Replies)
Discussion started by: paulexis
4 Replies
9. AIX
Guy's
I'm getting this message Livedump filesystem almost full in errpt logs
and its meanning this file system /var/adm/ras/livedump
/var has more than 1.5 GB free space ..
why I'm getting that message and .. Pls advice to to avoide it
---------- Post updated 03-21-11 at 01:39 AM... (1 Reply)
Discussion started by: Mr.AIX
1 Replies
LEARN ABOUT OPENSOLARIS
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1 A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.11 1 Mar 1994 queuedefs(4)