root partition was full and problem start

[unin89]

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 want to know what could be the probable reasons. Also what files I have to check on the server to see that they are in normal state.



Regards,

Rahul

More Information:

1. Add (n) a new primary partition (the start cyl defaults to the end of the /boot partition)
2. 15 posts - 5 authors - Last post: Sep 5, 2007The first clue that I found out the root partition was close to full was when I tried to install ATI driver using the ati's installer and it returned a message that there
3. 22 posts - 14 authors - Last post: Apr 11, 2005Now the problem is that the root file system is showing 97 %
4. I think the solution is just simply to create a bigger / partition from the start
5. Accidentally, the root flag (/dev/sda9) indicates that the root partition is the same as the one containing the kernel image
6. Problem - my root partition is suddenly full ???, How do know what to delete?
7. The new administrator deletes the file, but the system still complains that the partition is full
8. Of course this is a problem of mine: I didn't clean up my small root partition (due to historical reasons I have a small root partition and two big ones for
9. 04 and later include ext4 as a manual partitioning option at installation time, including support for ext4 as the root filesystem

More:

• How to duplicate a drive in Unix?
• Redhat 7.1 on Dell Inspiron laptop
• VIA USB, kudzu, and linksys NIC....
• Stability Problems on KT266 based system
• Turtle Beach Montego II / Linux
• Ati All-in-wonder 128 Pro
• Compatible Linux Modems
• GOOD NEWS for HCF modem !,, read on...
• USB Camera needs SCSI?!
• Sound Problems - Thinkpad

[trandu_tkqn]

Your full file system is the problem. You must check for what happened to fill it up and then decide what to do about it so it will not happen again.



Check your /var/adm/messages file for possible clues - if you have access to SunSolve, search for "filesystem full" or "/ full no login"- It gives different possible problems - one may be this:



This is caused by a full file system and the system has no space

to write its utmpx (login info) entry.



To get around this condition the system must be booted up

into single user mode. Then clear (do not delete) the files:



/var/adm/utmp

/var/adm/utmpx



This can be done by typing:



#cat /dev/null > filename



This command will zero out the file but keep it there with

the correct permissions.



In some cases after removing these files your /var filesystem may

still be full. In this case type:



du -askd /var |sort -nr |more



This will give you a listing of the files from largest to smallest

on the /var filesystem.



In order to create space you may zero out the following files:



/var/cron/log

/var/spool/lp/logs

/var/adm/messages



You may also check the following for any large files that can be deleted:



/.wastebasket

/lost found



----------------------------------------------------

Subsequent logins should work fine after this.



Keywords: var, umptx, wtmpx, utmp, wtmp







full file system



changing a flat filesystem

More Information:

1. net/rb/), mount your root partition to a temporary mount point, change your root to it and then reinstall
2. The root partition should be located within the first 8GB on the HDD (at least on versions of Knoppix that use the LILO bootloader)
3. How do I extend (enlarge) the root partition which is located on a logical volume, the problem being that you can't umount the root partition
4. Using the alternative CD, the /boot directory is, by default, placed on the root filesystem instead of on it's own partition
5. If you don't know the root partition then run this command to get a list of diff
6. 2 posts - 2 authors - Last post: Oct 17, 2008[Novalug] Still a Problem: re: full root partition problem

[linhxuankhanh]

Thanx for the ans. The null writting over utmp and wtmp has already done. Also the space has been made on the root file system. Still the problem persist.



Regards,

Rahul

More Information:

1. The trick here is to change the mount options for the root partition to mount it read-write without actually unmounting it, like this:
2. I went through and tried to start again, ut same problems
3. If you have WINXP installed to MBR on your hard drive, install LILO to the root partition instead of the MBR
4. The files are reloaded (or a portion of the files are loaded) and someone notices that the root filesystem is full or close to full
5. If you only have a / partition, it will be harder to find what is causing the problem
6. the mbr which points to the kernel in the root directory (/) has not moved so it _should boot right up_ problem is if you sign
7. View Full Version : problem with boot from raid - How To Set Up Software RAID1 on a running system (etch)

[taran2581982]

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

More Information:

1. sudden I can no longer start KDE or GNOME since my root partition is full
2. Is it possible using any Hp tool/software to online extension of the root partition without disturbing the exsting data on the volumes ?
3. The major problem will manifest itself after the kernel has finished loading and wants to start /sbin/init
4. 12 posts - 6 authors - Last post: Jan 7, 2009search your device name (da0 or something) and you see what is the full name of the pfsense partition
5. My suggestion is quite simple : just modify partmon iniscript to remove a 50MB file in / if the root partition is full and the file already exists
6. Package: udev Version: 146-5 Severity: important Since about one week, the UUID of the root partition is no longer detected
7. When the root filesystem is mounted, you can start breathing: you can at least use your swiss army knife with its sh, sed, and awk blades
8. For example, if the kernel in question was built on a system that used `/dev/hda1' as the root partition, then the default root device would be `/dev/hda1'
9. It is now possible to encrypt an entire Linux system, including root, the boot partition, and even the kernel itself
10. Xen Guest Boot Problems Building a Xen Guest Root Filesystem using yum and rpm - An Overview of Repository Based Installation