Sponsored Content
Operating Systems Solaris Solaris 10 spac root 76% full Post 302304030 by choogendyk on Saturday 4th of April 2009 01:23:22 PM
Old 04-04-2009
Here's an interesting option. Since you have available disk space that could be formatted for larger partitions, use live update to create an alternate boot partition and then switch to it.

If you aren't familiar with it, there is a good example with explanations at BigAdmin Sun Docs: How To Use Solaris Live Upgrade to Install Patches. It has references at the end to the online documentation at Sun. You can follow the example and just skip the patches, adjusting it to your situation.
 

8 More Discussions You Might Find Interesting

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

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

3. Linux

/root filesystem size is full

hi in my server ( / ) root filesystem size is full how to reduce the size and what are the files i want to remove. i need answer for linux and AIX also. (6 Replies)
Discussion started by: chomca
6 Replies

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

5. Solaris

root directory is full

root directory in server / is full 100% , i already tried to delete any core file , log , .. still files under /proc directory take more than 4 G.. what you advice please i don't want to format the server and install again and re partition , i tried the FORMAT tools ! but it seems i cant do... (5 Replies)
Discussion started by: moata_u
5 Replies

6. UNIX for Dummies Questions & Answers

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... (3 Replies)
Discussion started by: PUSHPARAJA
3 Replies

7. Solaris

User want to full root permission

hi guys.. how to give root permission for particular user tel me step by step (2 Replies)
Discussion started by: coolboys
2 Replies

8. Red Hat

ROOT fs is full but no files consumed more space

one our linux machine root fs usage shows 90% but inode use % i sarched more then 10 MB files and found few with less mb,s any once help to solve this $ df -h / Filesystem Size Used Avail Use% Mounted on /dev/cciss/c0d0p3 3.9G 3.3G 409M 90% / $ df -i /... (9 Replies)
Discussion started by: venikathir
9 Replies
cleanup(1M)															       cleanup(1M)

NAME
cleanup - HP-UX patch cleanup utility SYNOPSIS
DESCRIPTION
The command provides functions useful when dealing with HP-UX patches on HP-UX. The command logs all information to Options recognizes the following options: Preview the task but do not actually perform the requested action. Notify the user of tasks and request confirmation before performing the requested action. Commit patches superseded at least number times. This option is a front-end to the option of (see swmodify(1M)) that provides an easier interface to commit multiple patches at once. Remove patches in the specified software depot that have been superseded by patches also available from the depot. Specifies whether the software depot contains patches for HP-UX 10.X or 11.X releases. This option is only valid with the option. If the option is not specified, it defaults to HP-UX 11.X patches. Specifies whether patches in the software depot that contain a corequisite or prerequisite attribute specifying one of the superseded patches as a dependency should also be removed. This option is valid only with the option. If the option is not specified, it defaults to true. Remove HP-UX 10.X patches that remain in the Installed Product Database after an upgrade to HP-UX 11.X. These patches are removed from the IPD so that they are no longer displayed in the output of the command (see swlist(1M)). The HP-UX 10.X patch files are also removed from Correct the attribute for HP-UX 11.X patches. Recommendations The command should be executed after updating to HP-UX 11.X from HP-UX 10.20. It is not necessary to execute after updating from one ver- sion of HP-UX 11.X software to another because SD-UX will properly remove 11.X patch information from the IPD in these situations. The command should be executed whenever patches are added to a software depot. It is not a requirement that superseded 11.X patches be removed from a software depot, but it is a recommendation to conserve disk space and to avoid confusion. If superseded patches exist in the same depot as patches that supersede them, SD-UX on HP-UX 11.X will handle the situation properly. The command can be executed to commit all patches that have been superseded at least the specified number of times. The only benefit from committing patches is that disk space will be recovered in the The command can be executed to insure that the attribute of all patch filesets is set correctly. There are several known situations where the attribute will be set incorrectly. This command can be run at any time, but will be most useful after a system has been installed using Ignite-UX. AVAILABILITY
This command is standard on HP-UX 11i v3. On 11i v2 it is available in patch PHCO_32220 or a superseding patch. On 11i v1 it is available in patch PHCO_27780 or a superseding patch. WARNINGS
Extreme care should be used when committing patches. Once a patch has been committed, it cannot be removed from the system. Patches should only be committed when you are satisfied with their behavior. Recovering disk space should not be the only factor considered when committing patches. AUTHOR
was developed by HP. SEE ALSO
show_patches(1), sysdiff(1), check_patches(1M), swlist(1M), swmodify(1M), swremove(1M), sd(4). cleanup(1M)
All times are GMT -4. The time now is 05:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy