Sponsored Content
Full Discussion: Full File System
Top Forums UNIX for Advanced & Expert Users Full File System Post 29996 by janr on Tuesday 15th of October 2002 10:42:21 AM
Old 10-15-2002
A full / filesystem give always trouble.
I think the fact of a full root , is the reason you cannot boot single user

Iam afraid you need to boot from CD-rom.

be happy, up to now there is no reason for re-install your box, but its is the only way to get access to your disks.

Do you have a CD on your desk with the right OS level.
be carefull, boot from CD by typing `boot cdrom` on the OK prompt.

I never did this using Solaris 2.8, you had to stop the installation proces and you need a shell.

When you on the shell run fsck on all 'known' filesystems.
After you ran fsck you can mount your root filesystem and clean it.
check /tmp, /usr/tmp, /var/adm, /var/mail, etc

Good luck, post your progress maybe we can help in the meantime
 

9 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

file system full

When I try to log in as root I get the following message realloccg /: file system full sendmail :NO Queue:low on space (have 0,SMTP-DAEMON needs 101 in /var/spool/mqueue) What should I do? (1 Reply)
Discussion started by: hopeless
1 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

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

5. 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

6. 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

7. Solaris

/ file system full issue

Hi All, This is Babu working as a system administrator. Here I am getting one problem with one of my Sun server's root (/) file system. In df -h command / file system showing 7.8 GB used space.But in du -hd command it showing 5.2 gb only. Please can any one help me resolve this issue... (2 Replies)
Discussion started by: lbreddy
2 Replies

8. UNIX for Advanced & Expert Users

/opt file system full !!!

Can anyone help me in cleaning /opt filesystem.. i have checked all the options and i have cleared all the logs and the total size of the files in /opt is shown as 1.8GB were as the size of /opt is 4.8GB but wen i run the command # df -h /opt it gives capacity 99% Please help... (17 Replies)
Discussion started by: kjamsheed
17 Replies

9. Red Hat

File system full, but not really.

Hey all, What do you think mostly happened in the following situation? I have a Red Hat 5.5 server. Someone, somehow, managed to get two .nfs000.... type files that totaled over a terabyte in size. I removed them and thought things were back to normal. Then I started getting complains from... (2 Replies)
Discussion started by: geelsu
2 Replies
rcS(5)							   Debian Administrator's Manual						    rcS(5)

NAME
rcS - variables that affect the behavior of boot scripts DESCRIPTION
The /etc/default/rcS file contains variable settings in POSIX format: VAR=VAL Only one assignment is allowed per line. Comments (starting with '#') are also allowed. OPTIONS
The following variables can be set. For the default values please see /usr/share/initscripts/default.rcS. TMPTIME On boot the files in /tmp will be deleted if their modification time is more than TMPTIME days ago. A value of 0 means that files are removed regardless of age. If you don't want the system to clean /tmp then set TMPTIME to a negative value (e.g., -1) or to the word infinite. SULOGIN Setting this to yes causes init to spawn a sulogin on the console early in the boot process. If the administrator does not login then the sulogin session will time out after 30 seconds and the boot process will continue. DELAYLOGIN Normally the system will not let non-root users log in until the boot process is complete and the system has finished switching to the default runlevel (usually level 2). However, in theory it is safe to log in a bit earlier, namely, as soon as inetd has started. Setting the variable to no allows earlier login; setting the variable to yes prevents it. Some details: The DELAYLOGIN variable controls whether or not the file /var/lib/initscripts/nologin is created during the boot process and deleted at the end of it. /etc/nologin is normally a symbolic link to the latter location, and the login(1) program refuses to allow non-root logins so long as (the target of) /etc/nologin exists. If you set the variable to no then it is advisable to ensure that /var/lib/initscripts/nologin does not exist. UTC This is used to govern how the hardware real time clock is interpreted when it is read (e.g., at boot time, for the purpose of set- ting the system clock) and when it is written (e.g., at shutdown). If this option is set to no then the system clock is assumed to be set to local time. If the option is set to yes then the system clock is assumed to be set to something approximating Coordinated Universal Time (UTC). (POSIX systems keep a variant of UTC, without leap seconds.) On contemporary Debian systems (although change has been requested at http://bugs.debian.org/346342), if UTC is set to no then /usr/share/zoneinfo must be readable early in the boot process. If you want to keep /usr on a separate filesystem then you must still ensure that the target of /etc/localtime points to the correct zone information file for the time zone of the time kept in your hardware real time clock. VERBOSE Setting this option to no (in lower case) will make the boot process a bit less verbose. Setting this option to yes will make the boot process a bit more verbose. FSCKFIX When the root and all other file systems are checked, fsck is invoked with the -a option which means "autorepair". If there are major inconsistencies then the fsck process will bail out. The system will print a message asking the administrator to repair the file system manually and will present a root shell prompt (actually a sulogin prompt) on the console. Setting this option to yes causes the fsck commands to be run with the -y option instead of the -a option. This will tell fsck always to repair the file sys- tems without asking for permission. NOTE
The EDITMOTD and RAMRUN variables are no longer used. AUTHOR
Miquel van Smoorenburg <miquels@cistron.nl> SEE ALSO
inetd(8), init(8), inittab(5), login(1). 16 Jan 2006 rcS(5)
All times are GMT -4. The time now is 10:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy