The fundamental building block of UNIX file systems (including Linux’s ext2/ext3) is the i-node. An i-node is a control structure that points either to the other i-nodes or to data blocks.
The control information in the i-node includes the file’s owner, permissions, size, time of last access, creation time, group ID, etc. ( the entire kernel data structure is available in /usr/src/linux/include/linux/ext3_fs.h—assuming, of course, that you have the source tree installed in the /usr/src directory.) The one thing that an i-node doesn"t keep is the file’s name.
While the directories themselves are special instances of the files. And this means that each directory gets an i-node, and further the i-node points to data blocks containing information (filenames and i-nodes) about the files in the directory. The i-nodes are used to provide the indirection so that more data blocks can be pointed to—which is reason why each i-node does not
contains the filename. (Only one i-node works as a representative for the entire file which contains the filename; thus it would be a waste of the space if every i-node contains the filename information.) Each indirect block can be used to point in turn to other indirect blocks if necessary.
Superblocks:-
The very first information which is read from a disk is its superblock. This small data structure reveals the several key pieces of the information, which includes the disk’s geometry, the amount of available space, and, most important of the all, the location of the first i-node. In the absence of a superblock, a file system is useless.
Something as important as the superblock cannot be left to the chance. Thus the Multiple copies of this data structure are scattered all over the disk to provide backup in case the one is damaged. Under the Linux’s ext2 file system, a superblock is placed after every group of blocks, which contains an i-nodes and data. One group consists of 8,192 blocks; thus this means the first redundant superblock is at 8193, the second at 16385, and so on.
Blogroll
Glossary
Installing Linux On a Server
- Installing and configuring Vmware2 to Run Linux (R...
- Installing Linux in a Server Configuration
- Performing Preinstallation Evaluation
- Linux System Administrator
- Installing and Configuring Servers
- Installing and Configuring Application Software
- Creating and Maintaining User Accounts
- Backing Up and Restoring Files
- Monitoring and Tuning Performance
- Configuring a Secure System
- Using Tools to Monitor Security
- Server Design
- Uptime
- Dual-Booting Issues
- Methods of Installation
- Determining a Server’s Functions
- Using the Red Hat Package Manager
- Initialization Scripts
Network Configuration
Filesystem Primer
- Understanding Filesystem Hierarchy Standard
- Basic Linux Directory Structure
- Partition Schemes
- Managing Partitions
- Managing partitions with fdisk
- Adding A New Hard Drive
- Basic Linux Formats
- Formatting a partition
- Tuning
- Troubleshooting With FSCK
- Exploring Logical Volume Management
- File Permissions 1
- File Permissions 2
- umask
- Concept of the i-Nodes and Superblocks in Linux/Un...
- Understanding ext3 file system and its advantages
Administering Users and Groups Securely
Network File System
Concept of the i-Nodes and Superblocks in Linux/Unix System
5:54 AM | Filed Under Filesystem Primer | 0 Comments
Comments
Install Softwares
- Install Vuze(Azureus) Bittorent client on Linux 64..
- Install Skype(pc2pc calling software) On Linux 64 ...
- Install WEBMIN to Graphically Administer Your Linu...
- Opening And Extracting .rar Files in Linux/Unix sy...
- Installing vlc player in Fedora/Red Hat/ CentOS
- Linux text to speech festival
- Installing Thunderbird E-mail client
Post a Comment