Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory root partition was full and problem start Post 25924 by RTM on Wednesday 7th of August 2002 04:28:32 PM
Old 08-07-2002
How are your partitions laid out? Does the server boot to multiuser mode? What processes are starting automatically that could be opening up or grabbing space (check /etc/rc2.d, /etc/rc3.d, and cron jobs)?

If you only have a / partition, it will be harder to find what is causing the problem. If you can't use the server, then start looking for the problem - boot the server into single user mode. Check to see if the problem exist. If not, then something is starting up in multiuser mode. Check your startup scripts and cron jobs. Maybe someone made a change and didn't realize they caused a problem.

Post back the partitions and any software you might be using for mirroring etc..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

root partition full and problem start

We have SunOS 5.7 m/c. Following is the situation and problem what we are facing - - The root partition was full. - No login was possible on server (not from console also) - M/c was power swithced off - After this only console login is possible. FTP is possible. No telnet is possible. I... (1 Reply)
Discussion started by: rahul72
1 Replies

2. UNIX for Dummies Questions & Answers

Full Partition?

Hi Everyone, I think I've filled up one of the partitions on my drive. I suspect that one of the applications I've been running has been spitting out junk files to this partition - most of which can be deleted. The problem is that I have no idea how to go look at what's on that partition and... (2 Replies)
Discussion started by: Choppy
2 Replies

3. UNIX for Advanced & Expert Users

Hard-disk partition is Full problem?

HI, Currently I am working in One of the webhosting company and I found on one of my server "/home" partition is getting full say 105% usage... But when I actually check the partition size using "du -h", exact partition utilization is only 60-70%. So... (1 Reply)
Discussion started by: jagdish.machhi@
1 Replies

4. Solaris

Help: root partition crashed, fsck failed. Disk problem?

recently this sunfire 280R (solaris 10) is having problme, it was able to boot up, then all suddent, it failed, and I can't even mount the first disk which contains root partition when I boot up from cdrom. 2 X 36G hard drive, I scan first hard drive by "read", there is no bad block. The... (2 Replies)
Discussion started by: steeles
2 Replies

5. Solaris

Problem creating full root zones

OK, the situation is that I am trying to avoid full root zones whenever possible but I need at least /usr writable as this zone will be using apache as installed as a Solaris package. So....I created a new zone and every time I try to remove any inherited package directories, the below occurs.... (2 Replies)
Discussion started by: LittleLebowski
2 Replies

6. HP-UX

effect of full root partition on server

hi, I want to know that "What Happen if the root partition gets full on the server? I have HP-Unix 11.11 installed. (3 Replies)
Discussion started by: majidtahir
3 Replies

7. HP-UX

/var partition full need help

My /var partition is almost utilized ... Here am not sure where to release space now OS/model : HP-UX B.11.11 U 9000/800 # bdf /var Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol9 6144000 6142176 1824 100% /var <root@pb>/var # du -sk * | sort -n |... (20 Replies)
Discussion started by: Shirishlnx
20 Replies

8. Solaris

Need to partition root

Hello guys, I am using Solaris 10 x86 OS. While installing OS i have allocated entire 10 GB space to the root. Now i am not able to create new partition it says me "out of range" or "<cylinder number> not expected". Can someone please help me to allocated a default recommended space i.e 8GB or... (2 Replies)
Discussion started by: bhargav90
2 Replies

9. Red Hat

Warning: extended partition does not start at a cylinder boundary.

Can you please help me to remove this error. Disk /dev/sda: 64.4 GB, 64424509440 bytes 255 heads, 63 sectors/track, 7832 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk... (4 Replies)
Discussion started by: karthik9358
4 Replies

10. UNIX for Beginners Questions & Answers

TRU64 - Cluster boot partition is FULL

Good day, Anybody, know how to clean/free up the Cluster_boot partition in TRU64 Thank you in advance Miaka (0 Replies)
Discussion started by: miaka1012
0 Replies
queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and crontab SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue. The format of the lines are as follows: [njob[nice[nwait The fields in this line are: q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by (see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined queues. njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed by setting the variable to 1 in the file. nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). 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 more than 100 jobs were running in all the queues (see njob above). EXAMPLES
Consider the following file: The file is interpreted as follows: The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of 1. Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it (see cron(1M)). The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2. If a job cannot be run because too many other jobs are running, 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 value of 2, and if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it. SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4). STANDARDS CONFORMANCE
queuedefs(4)
All times are GMT -4. The time now is 01:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy