Sponsored Content
Operating Systems AIX 100% Inode full with only 67% FS full. Post 302983111 by rbatte1 on Thursday 6th of October 2016 12:01:28 PM
Old 10-06-2016
Smilie I would seriously worry why you think you need a 12Gb root filesystem. Smilie

You should only have files necessary for the OS boot in the root filesystem, ideally with home directories, /usr, /var and /tmp in separate filesystems. Perhaps you should focus on removing non-OS files from the root filesystem.

How do you prepare for disaster recovery? Is your mksysb excluding huge sections of the root filesystem? If so, it would be better to get them into their own filesystems and leave root alone. Have a look in /etc/exclude.rootvg to see what you leave out of a mksysb



Robin
 

9 More Discussions You Might Find Interesting

1. AIX

%Inode used full

Hello I have used 100% of inode in a file system can you increase thie number of inode without backup-make the file system again-restore ? thank you (0 Replies)
Discussion started by: pascalbout
0 Replies

2. Solaris

/ directory is 100% full

Dear experts My / directory shows 100% full. What should I do??? What is normal size and how can I prevent it. I am using Solaris 8 on an Ultra 60. Thanks for your advises. Reza (6 Replies)
Discussion started by: Reza Nazarian
6 Replies

3. Solaris

when 100% full, it says some available

Just a quick question ....as per my df -k below, I have a file system marked at 100% full, why does it say there is 44,240 kb available ?? Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 2055463 1753694 240106 88% / /proc 0 ... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

4. AIX

/var 100% full

What to do if /var filesystem in Aix is completely full ? (2 Replies)
Discussion started by: kkhan
2 Replies

5. Linux

Disk full 100%

one of my servers / was full by 100% i cleard some space, now though i have enough space on / partition still df is showing disk usage as 100% am not able to create any single txt file ? why so ? (3 Replies)
Discussion started by: bryanabhay
3 Replies

6. UNIX for Dummies Questions & Answers

dev/sda1 100% full

Hi! I have a problem with my disk, it is full as you can see # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 64380356 63125180 0 100% / none 3116000 0 3116000 0% /dev/shm /dev/sdb1 282015652... (10 Replies)
Discussion started by: ruisof
10 Replies

7. Shell Programming and Scripting

How to extract strings from full path when full path is not fixed

/Path/snowbird9/nrfCompMgrRave1230100920.log.gz:09/20/2010 06:14:51 ERROR Error Message. /Path/snowbird6/nrfCompMgrRave1220100920.log.gz:09/20/2010 06:14:51 ERROR Error Message. /Path/snowbird14/nrfCompMgrRave920100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.... (0 Replies)
Discussion started by: Shirisha
0 Replies

8. AIX

Paging space is 100% full

Paging space is 100% full? what step can i take (3 Replies)
Discussion started by: ramraj731
3 Replies

9. Solaris

Zpool showing 100% full

Hi, This is Solaris-10 on Sparc. Due to some reason, one zpool size is showing 100% full, while nothing is there in that. dstr03-zone02 is a non global zone running on physical machine - dstr03 root@dstr03:/# df -h | grep -i zone02 zone02_app_pool 60G 31K 3.8G 1% ... (5 Replies)
Discussion started by: solaris_1977
5 Replies
fs(4)							     Kernel Interfaces Manual							     fs(4)

NAME
fs, inode - Specifies the format of the file system volume SYNOPSIS
#include <sys/types.h> #include <sys/fs.h> #include <ufs/inode.h> DESCRIPTION
Every file system storage volume (disk, nine-track tape, for instance) has a common format for certain vital information. Each such volume is divided into a certain number of blocks. The block size is a parameter of the file system. Sectors beginning at BBLOCK and continuing for BBSIZE are used to contain a label and for some hardware primary and secondary bootstrapping programs. Each disk drive contains some number of file systems. A file system consists of a number of cylinder groups. Each cylinder group has inodes and data. A file system is described by its superblock, which in turn describes the cylinder groups. The superblock is critical data and is repli- cated in each cylinder group to protect against loss of data. This is done at file system creation time and the critical superblock data does not change, so the copies need not be referenced further until necessary. Addresses stored in inodes are capable of addressing fragments of blocks. File system blocks of at most MAXBSIZE size can be optionally broken into 2, 4, or 8 pieces, each of which is addressable; these pieces may be DEV_BSIZE, or some multiple of a DEV_BSIZE unit. Large files consist exclusively of large data blocks. To avoid wasted disk space, the last data block of a small file is allocated only as many fragments of a large block as are necessary. The file system format retains only a single pointer to such a fragment, which is a piece of a single large block that has been divided. The size of such a fragment is determined from information in the inode, using the blksize(fs, ip, lbn) macro. The file system records space availability at the fragment level; to determine block availability, aligned fragments are examined. The root inode is the root of the file system. Inode 0 (zero) can't be used for normal purposes and, historically, bad blocks were linked to inode 1. Thus, the root inode is 2 (inode 1 is no longer used for this purpose, but numerous dump tapes make this assumption). Some fields to the fs structure are as follows: Gives the minimum acceptable percentage of file system blocks that may be free. If the freelist drops below this level only the superuser may continue to allocate blocks. The fs_minfree field may be set to 0 (zero) if no reserve of free blocks is deemed necessary. However, severe performance degradations will be observed if the file system is run at greater than 90% full; thus the default value of the fs_minfree field is 10%. Empirically the best trade-off between block fragmentation and overall disk utilization at a loading of 90% comes with a fragmenta- tion of 8, thus the default fragment size is an eighth of the block size. Specifies whether the file system should try to minimize the time spent allocating blocks, or if it should attempt to minimize the space fragmentation on the disk. If the value of fs_min- free is less than 10%, then the file system defaults to optimizing for space to avoid running out of full sized blocks. If the value of fs_minfree is greater than or equal to 10%, fragmentation is unlikely to be problematical, and the file system defaults to optimizing for time. Cylinder group related limits: Each cylinder keeps track of the availability of blocks at different positions of rotation, so that sequential blocks can be laid out with minimum rotational latency. With the default of 8 distinguished rotational positions, the resolution of the summary information is 2 milliseconds for a typical 3600 rpm drive. Gives the minimum number of milliseconds to initiate another disk transfer on the same cylinder. The fs_rotdelay field is used in determining the rotationally optimal layout for disk blocks within a file; the default value for fs_rotdelay is 2 milliseconds. Each file system has a statically allocated number of inodes. An inode is allocated for each NBPI bytes of disk space. The inode alloca- tion strategy is extremely conservative. MINBSIZE is the smallest allowable block size. With a MINBSIZE of 4096 it is possible to create files of size 232 with only two levels of indirection. MINBSIZE must be big enough to hold a cylinder group block, thus changes to struct cg must keep its size within MINBSIZE. Note that superblocks are never more than size SBSIZE. The pathname on which the file system is mounted is maintained in fs_fsmnt. MAXMNTLEN defines the amount of space allocated in the superblock for this name. The limit on the amount of summary information per file system is defined by MAXCSBUFS. For a 4096 byte block size, it is currently parameterized for a maximum of two million cylinders. Per cylinder group information is summarized in blocks allocated from the first cylinder group's data blocks. These blocks are read in from fs_csaddr (size fs_cssize) in addition to the superblock. Superblock for a file system: The size of the rotational layout tables is limited by the fact that the superblock is of size SBSIZE. The size of these tables is inversely proportional to the block size of the file system. The size of the tables is increased when sector sizes are not powers of two, as this increases the number of cylinders included before the rotational pattern repeats (fs_cpc). The size of the rotational layout tables is derived from the number of bytes remaining in (struct fs). The number of blocks of data per cylinder group is limited because cylinder groups are at most one block. The inode and free block tables must fit into a single block after deducting space for the cylinder group structure struct cg. Inode: The inode is the focus of all file activity in the UNIX file system. There is a unique inode allocated for each active file, each current directory, each mounted-on file, text file, and the root. An inode is `named' by its device/i-number pair. NOTES
sizeof (struct csum) must be a power of two in order for the fs_cs macro to work. delim off fs(4)
All times are GMT -4. The time now is 02:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy