Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Root file system full..Need help Post 302559762 by PUSHPARAJA on Wednesday 28th of September 2011 05:12:03 AM
Old 09-28-2011
Root file system full..Need help

Hi guys,
In sun E250 server,root file system is full. we cleared log files in var/adm folder
syslogs,mail logs,crash logs are empty. This is a production server. we are not able to run fsck from single user mode. I have given output of df and du command.How to create space in root filesystem.Need help...

Code:
df -k
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/dsk/c0t12d0s0   2508929 2458876       0   100%    /
/devices                   0       0       0     0%    /devices
ctfs                       0       0       0     0%    /system/contract
proc                       0       0       0     0%    /proc
mnttab                     0       0       0     0%    /etc/mnttab
swap                 1348656    1064 1347592     1%    /etc/svc/volatile
objfs                      0       0       0     0%    /system/object
/dev/dsk/c0t12d0s3   6050982 3403797 2586676    57%    /usr
fd                         0       0       0     0%    /dev/fd
/dev/dsk/c0t12d0s4   5163909  332089 4780181     7%    /var
swap                 1351112    3520 1347592     1%    /tmp
swap                 1347640      48 1347592     1%    /var/run
/dev/dsk/c0t12d0s5   5163909 2608842 2503428    52%    /opt
/dev/dsk/c0t12d0s6   3098095    7902 3028232     1%    /home
/dev/dsk/c0t12d0s7   11006444 3284472 7611908    31%    /usr/local
rdz_vol1/exports     104251392      59 39926849     1%    /d0/exports
rdz_vol1/oracle      104251392 63688338 39926849    62%    /d1/app/oracle
mp_ora_d2            34836480      26 28888556     1%    /d2
mp_ora_d2/oradata    34836480 5947059 28888556    18%    /d2/oradata
rdz_vol1             104251392  627383 39926849     2%    /raid1


Code:
du -sk /*
5       /Desktop
1       /Documents
62      /TT_DB
1       /bin
1       /cdrom
1968938 /d0
63986207        /d1
5947061 /d2
541     /dev
108     /devices
56784   /etc
6       /export
4822    /home
34990   /kernel
4240    /letc
26650   /lib
8       /lost+found
2       /mnt
0       /net
1       /nsr
2603714 /opt
2       /oracle
209     /oradiag_root
23539   /platform
89929354        /proc
627543  /raid1
1       /restore
4       /root
9654664 /sa
1609    /sbin
1       /swapfile
1       /sysout
5649    /system
3592    /tmp
6671356 /usr
327048  /var
0       /vol


Thanks,
pushparaja

Last edited by pludi; 09-28-2011 at 06:52 AM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Full File System

Hi All, There was a background process running on a Solaris 2.8 machine, and appeared to have filled all available disk-space. I done a killall, and upon re-booting found that the file system had filled up, and will not boot as normal as a result. For example, I'm getting /usr/adm/messages: No... (8 Replies)
Discussion started by: Breen
8 Replies

2. Filesystems, Disks and Memory

root file system full

Hi I have a Solaris 2.5.1 system. Recently my file system is full and i couldn't find what flood my root file system. Anyone can suggext any directories i should look out for. I am using Samba and Patrol agent. I am just usng this server as a file server, users cannot login into the system,... (1 Reply)
Discussion started by: owls
1 Replies

3. Solaris

File system full?

Hi, I just started working with UNIX on an old semi-fossilized Sun workstation which I use to process LOTS of images,however, I just started to get an error message that the file system is full and then my shell tool or/and text editor freeze up. Help? (8 Replies)
Discussion started by: Bend
8 Replies

4. Solaris

Root file system is 82% full

Hi I want to find out the reason that why root partition is 82% full? when i did fu -k / then most of files were created on /var . can you please help me to find out what I need to do in order to find the reason. Regards Ajwat (2 Replies)
Discussion started by: Ajwat
2 Replies

5. Solaris

Full file system?

I read the sticky and thought of a script I use on a regular basis. Since unless you patch/upgrade the df command on solaris you have a very tought time teling how full the system truly is. Output looks like $ biggest.sh /tmp Filesystem kbytes used avail capacity Mounted... (0 Replies)
Discussion started by: meyerder
0 Replies

6. UNIX for Dummies Questions & Answers

Root directory full, system does not boot

Hi, I have an SGI workstation running on Irix 6.5. A few days ago the system started giving messages that the root directory is full. Even before I could find out how to clean up the root directory, the system crashed and does not boot anymore. Can anyone help me on how I can get the system to... (1 Reply)
Discussion started by: gnanavvk
1 Replies

7. UNIX for Dummies Questions & Answers

Root File System Full

Hi All, The root file system of the HP-UX serevr I use is showing as 100% full. It has a disk space of ~524MB. When I add up the sizes of all the files and directories (using du -sk) , except mount points, it came up to 237MB. But when I bdf it still shows 100% full Can anyone help... (3 Replies)
Discussion started by: sube
3 Replies

8. Solaris

file system full

I am receving following Error message in /var/adm/messages "NOTICE: alloc: /: file system full" Disk space usage is as beklow: df -k $ Filesystem kbytes used avail capacity Mounted on /dev/md/dsk/d10 76678257 56962561 18948914 76% / /proc ... (8 Replies)
Discussion started by: Asteroid
8 Replies

9. Solaris

file system full

hello Even though I am not out of inodes or of space, the /var/adm/messages shows messages: file system full I am doing now fcsk -m (400G) and I am still waiting to see the fragmentation results (should I add another option to df to have a faster output?) Do you have any other hints... (6 Replies)
Discussion started by: melanie_pfefer
6 Replies
syslog.conf(4)						     Kernel Interfaces Manual						    syslog.conf(4)

NAME
syslog.conf - syslogd configuration file SYNOPSIS
facility.severity destination Where: Is part of the system generating the message, specified in /usr/include/sys/syslog_pri.h. See also the syslogd(8) reference page. The severity level, which can be emerg, alert, crit, err, warning, notice, info, or debug. See /usr/include/sys/syslog_pri.h. The syslogd daemon logs all messages of the specified severity level plus all messages of greater severity. For example, if you specify level err, all messages of levels err, crit, alert, and emerg or panic are logged. A local file pathname to a log file, a host name for remote logging or a list of users. In the latter case the users will receive messages when they are logged in. An asterisk (*) causes a message to be sent to all users who are currently logged in. DESCRIPTION
The /etc/syslog.conf file is a system file that enables you to configure or filter events that are to be logged by syslogd. You can specify more than one facility and its severity level by separating them with semicolons. You can specify more than one facility logs to the same file by separating the facilities with commas, as shown in the EXAMPLES section. The syslogd daemon ignores blank lines and lines that begin with an octothorpe (#). You can specify # as the first character in a line to include comments in the file or to disable an entry. The facility and severity level are separated from the destination by one or more tab characters. If you want the syslogd daemon to use a configuration file other than the default, you must specify the file name with the following com- mand: # syslogd -f config_file Daily Log Files You can specify in the /etc/syslog.conf file that the syslogd daemon create daily log files. To create daily log files, use the following syntax to specify the path name of the message destination: /var/adm/syslog.dated/ { file} The file variable specifies the name of the log file, for example, mail.log or kern.log. If you specify a /var/adm/syslog.dated/file path name destination, each day the syslogd daemon creates a sub-directory under the /var/adm/syslog.dated directory and a log file in the sub-directory, using the following syntax: /var/adm/syslog.dated/ date / file Where: The date variable specifies the day, month, and time that the log file was created. The file variable specifies the name of the log file you previously specified in the /etc/syslog.conf file. The syslogd daemon automatically cre- ates a new date directory every 24 hours and also when you boot the system. The current directory is a link to the latest date directory. To get the latest logs, you only need to reference the /var/adm/syslog.dated/current directory. EXAMPLES
The following is a sample /etc/syslog.conf file: # # syslogd config file # # facilities: kern user mail daemon auth syslog lpr binary # priorities: emerg alert crit err warning notice info debug # kern.debug /var/adm/syslog.dated/kern.log user.debug /var/adm/sys- log.dated/user.log daemon.debug /var/adm/syslog.dated/daemon.log auth.crit;syslog.debug /var/adm/syslog.dated/syslog.log mail,lpr.debug /var/adm/syslog.dated/misc.log msgbuf.err /var/adm/crash.dated/msgbuf.savecore kern.debug /var/adm/messages kern.debug /dev/console *.emerg * FILES
/etc/syslog.conf /etc/syslog.auth - Authorization file for remote logging. /usr/include/sys/syslog_pri.h - Common components of a syslog event log record. RELATED INFORMATION
Commands: /usr/sbin/syslogd(8), /usr/sbin/binlogd(8) System Administration delim off syslog.conf(4)
All times are GMT -4. The time now is 09:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy