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
idisk(1M)																 idisk(1M)

NAME
idisk - create partitions for disks on an Integrity system SYNOPSIS
partition_description_file}] device DESCRIPTION
creates operating system partitions for disks on an Integrity system. It reads in the partition information from a data file that may be specified in the command string or redirected from stdin. By default, operates in read-only mode and displays the partition information that is currently on the disk. To write new partition infor- mation on the disk the user must specify the option. Options recognizes the following options: Print the primary EFI partition header and partition tables. Print the alternate EFI partition header and partition tables. Print the legacy partition table that resides in the master boot record. writes partition information for the first four partition in the partition table in used by legacy DOS and Win- dows. This information is used as a backup in the event all the EFI information is corrupted. Print the first usable and last usable block numbers that are available to create partitions. First usable is the first block a partition can start on. Last usable is the last block that can be contained in a partition. These numbers are relative to the whole disk and do not take into account any partitions that may exist. They represent the total disk space that can be partitioned. Use the option to only print the values without headings. Work silently. No user prompts or warnings. For use in shell scripts. Validate EFI partition information. Does the same checks the driver does verifying that both the primary and alternate EFI partition headers and tables are correct. Returns two if either is bad and zero if both are correct. Restore the EFI partition headers and tables. This option checks both the primary header and tables and the alternate header and tables. If one is found bad it is restored from the other good ver- sion. One of either the primary or alternate header and tables must be good for this option to succeed. The option must be specified for information to be written to the disk. Remove all EFI partition headers and tables from the disk. This option also destroys the information contained in the MBR (master boot record). The option must be specified for information to be written to the disk. The partition_description_file contains the number of partitions to be created and the type and requested size of each partition. The filename may be specified here or redirected from stdin when the dash is used. Enable write mode. By default operates in read-only mode. To create and write partition information to the disk you must specify the option. Partition Description File The first entry in the partition description file is the number of partitions to create. The maximum number of partitions allowed is 12. This is followed by a line containing the type and size for each of the partitions. Recognized partition types are: and At least one EFI partition is required to create a valid partition table. Size may be specified in megabytes or as a percentage of the whole disk. Internally, creates the partitions whose size is specified in MB first then creates those whose size was specified as a percentage. Those partitions specified as a percent are assigned space from what is available after the MB partitions are created. If the size of a parti- tion is specified as 100% then all space remaining is assigned to that partition. An example partition description file is shown below: The first entry specifies the number of partitions to create. The second specifies an EFI partition of 100 megabytes. The last entry specifies a HPUX partition consisting of all the remaining space on the disk after the EFI partition has been created. When creating partitions, the device file name must be that of the whole disk. Legacy device files must not have any partition number bits set in the minor number. For legacy disk devices, the last eight bits of the minor number represent the option bits. For Integrity system disks, the last four option bits are used to indicate the partition number. Since there are only four bits for parti- tion number, only one to fifteen partitions are supported. For example, a device node with a minor number of 0x008001 would indicate a disk at target eight, partition number one. A minor number of 0x00500F would indicate a disk at target 5 partition fifteen. A minor num- ber with no partition bits set would indicate the whole disk (for example, 0x008000 would be the same disk as above but represent the whole disk and not a partition). Persistent device special files do not use or contain minor number information. A detailed description on persistent device special files can be found in intro(7). Note: For partitions created by device special files must be created for each legacy hardware path to the disk and for the LUN hardware path using or (see intro(7) for details on legacy and agile modes). If legacy mode is disabled (see the descrip- tion of the option in rmsf(1M)), device special files must only be created for the LUN hardware path. Note has been ported to Windows NT 4.0 and 2000. RETURN VALUE
Exit values are: Successful completion. Error condition occurred. EXAMPLES
Create the partitions specified in the above description file, printing only the primary partition information: Create the partitions specified in the above description file, printing only the primary partition information using a persistent device special file (see intro(7)): Create the partitions specified in the above description file, printing all available information (default), redirecting input from stdin: Only read the disk, printing all tables (default) on the disk: Get the first and last usable block for partitioning on the disk: Destroy all partition information on the disk: Restore partition information from either a good primary or alternate header or table to the header or table that is bad: AUTHOR
was developed by HP. SEE ALSO
insf(1M), mksf(1M), efi(4), intro(7). Integrity Systems Only idisk(1M)
All times are GMT -4. The time now is 07:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy