i-nodes In Linux

By -

What is inode?
In computing, an index-node (inode) is a data structure on a traditional Unix-style file system such as UFS. An inode stores all the information about a regular file, directory, or other file system object, except its data and name.(as defined in Wikipedia)

The Inode is a pivitol structure within the Unix filesystem. The purposes of an inode is to hold all the information about a file you would normally expect to see in a directory entry on another system - file size, location, access & modification times, ownership, etc. To exist in a filesystem every file must have a inode. Directories, symbolic links, device files and pipes all have inodes.


When the inode table is full so is your filesystem, no matter what 'df' is saying about the amount of free space. The size of the inode table is fixed when it is created, there is no command to extend it. Solaris users can examine the state of their inode table using the 'df -e' command.
The following example shows the Linux syntax;
root@root-pc:~# df -i
Filesystem             Inodes    IUsed    IFree          IUse%     Mounted on
/dev/hda2            179520   75798  103722      43%             /

How to Free Inode Usage


It's quite easy for a disk to have a large number of inodes used even if the disk is not very full.
An inode is allocated to a file so, if you have gazillions of files, all 1 byte each, you'll run out of inodes long before you run out of disk.
It's also possible that deleting files will not reduce the inode count if the files have multiple hard links. As I said, inodes belong to the file, not the directory entry. If a file has two directory entries linked to it, deleting one will not free the inode.
Additionally, you can delete a directory entry but, if a running process still has the file open, the inode won't be freed.
My initial advice would be to delete all the files you can, then reboot the box to ensure no processes are left holding the files open.


Comments

Post a Comment

Popular posts from this blog

CEPH bluestore using ceph-ansible

By -
Just to test the ceph bluestore i have created 2 virtual machine in virtualbox with hostname: admin & osd1. Attached the 2 10G hdd for the OSD's in both the nodes. Below are the commands that i used to deploy it using the ceph-ansible: git clone https://github.com/ceph/ceph-ansible cd ceph-ansible cp group_vars/osds.yml.sample group_vars/osds.yml cp group_vars/all.yml.sample group_vars/all.yml cp group_vars/mons.yml.sample group_vars/mons.yml cp site.yml.sample site.yml vi group_vars/osds.yml     devices:    - /dev/sdb     - /dev/sdc bluestore : true vi group_vars/all.yml ceph_stable: true ceph_mirror: http://download.ceph.com/ ceph_stable_key: https://download.ceph.com/keys/release.asc ceph_stable_release: kraken ceph_stable_repo: "{{ ceph_mirror }}/rpm-{{ ceph_stable_release }}" monitor_interface: enp0s3 monitor_address: 192.xx.xx.xx osd_objectstore: bluestore ceph_conf_overrides:  ...
Read more

Start wildfly service with standalone-full.xml

By kris -
Wildfly provides a service.bat in %WILDFLY_HOME%\bin\service. Calling the batch file with the install parameter installs Wildfly as a service on Windows. Once it is installed on windows, you can change the settings so that wildfly starts all the modules and services instead of default minimal setup. For this, change standalone.bat file and add this line : set "SERVER_OPTS=--server-config=standalone-full.xml" This will enable startup of all modules & services of wildfly from now on.
Read more

Scan FC LUN's in RHEL/CentOS

By -
1.First find out how many disks are visible in “fdisk -l” . # fdisk -l 2>/dev/null | egrep '^Disk' | egrep -v 'dm-' | wc -l 2.Find out how many host bus adapter configured in the Linux box.you can use “systool -fc_host -v” to verify available FC in the system. # ls /sys/class/fc_host host0 host1 In this case,you need to scan host0 & host1 HBA. 3.If the system virtual memory is too low ,then do not proceed further.If you have enough free virtual memory,then you can proceed with below command to scan new LUNS. # echo "1" > /sys/class/fc_host/host0/issue_lip # echo "1" > /sys/class/fc_host/host1/issue_lip Note:   You need to monitor the “issue_lip” in /var/log/messages to determine when the scan will complete.This operation is an asynchronous operation. 4.Verify if the new LUN is visible or not by counting the available disks. # fdisk -l 2>/dev/null | egrep '^Disk' | egrep -v 'dm-' | wc -l If any new...
Read more