Results 1 to 6 of 6

Thread: Inode number and file structure in Linux

  1. #1
    Join Date
    Jul 2010
    Posts
    25

    Inode number and file structure in Linux

    I have recently started working with the Linux, so I am not having enough idea about it. I want to know about the inode number and file structure in Linux. I am sure that you members will help me. It would be much better if someone provides me more information about the topic. As I have mentioned that I am newbie in this field, please explain me in details.

  2. #2
    Join Date
    Jan 2009
    Posts
    143

    Re: Inode number and file structure in Linux

    The inode number identifies a file, which can receive different names. Inodes are nodes of information that are coupled with the name of a file. The list of the inodes and information management files are placed in the first blocks of the data carrier in order to accelerate access to files.
    • Block 0 is the boot block (block BOOT) that contains the initialization files of the operating system.
    • Block 1 is the "superblock" which contains information about the file structure.
    • Blocks 2 to n contain the list of "n-1" i-nodes.
    • Blocks of n +1 to z contain the data.

  3. #3
    Join Date
    Dec 2008
    Posts
    161

    Re: Inode number and file structure in Linux

    I would like to provide an information about file structure in Linux:
    • The physical block size
    • The logical block size (allocation unit)
    • The name of the physical media ("/ dev/hda1" for the first IDE hard disk)
    • The switch detailing the status of the structure
    • The name of the structure ("/" for root root)
    • The possible number of i-nodes
    • The actual number of inodes
    • The pointer to the first free inode
    • The pointer to the first block of free data

  4. #4
    Join Date
    Dec 2008
    Posts
    202

    Re: Inode number and file structure in Linux

    I would like to provide an information about file structure in Linux:

    * The physical block size
    * The logical block size (allocation unit)
    * The name of the physical media ("/ dev/hda1" for the first IDE hard disk)
    * The switch detailing the status of the structure
    * The name of the structure ("/" for root root)
    * The possible number of i-nodes
    * The actual number of inodes
    * The pointer to the first free inode
    * The pointer to the first block of free data
    When the file is very large, some places refer to another block which may also contain another block address. This principle is called "indirection" and it is valid for three levels, so there is a larger number of possible addresses (126x126x126).

  5. #5
    Join Date
    Oct 2008
    Posts
    167

    Re: Inode number and file structure in Linux

    In Linux, all objects in the tree are considered a file. There are different types of files:
    • Files (-)
    • Directories (d)
    • Devices (Device Number Major, Minor device number)
      • Block devices (b). The block devices (like hard disks, CDROM drives) maintains a certain amount of byte at a time, by block group.
      • The peripheral character (c). The character devices (like mouse, keyboard, serial port, parallel port) runs a character transmitted at a time.
    • FIFO communication channels pipes (p)
    • The socket (s)
    • Links (l)
    Most file types have been cataloged and identified by a magic number in / usr / share / magic.

  6. #6
    Join Date
    Mar 2008
    Posts
    258

    Re: Inode number and file structure in Linux

    Access rights or permissions can restrict certain users or groups of users access to certain files or directories. There are three types of access rights:
    1. read (r) for read access to the file (allows printing, viewing and copying a file, and allows the passage of the directory or display files from a directory)
    2. write (w) for write access to the file (you can change a file, and allows the deletion of a file or saving a file in a directory)
    3. execute (x) the ability to run the file (allows the execution of a program, an executable, and provides access to management information files directory, such as the inode table of fees).

Similar Threads

  1. Need to understand the Linux Directory Structure
    By Kensington in forum Operating Systems
    Replies: 5
    Last Post: 04-01-2011, 12:12 AM
  2. The \$Extend\$RmMetaData\file structure
    By August59 in forum Operating Systems
    Replies: 10
    Last Post: 15-05-2010, 11:41 PM
  3. Structure of Windows Registry file
    By Elieis in forum Windows Software
    Replies: 3
    Last Post: 18-11-2009, 12:43 AM
  4. I need to restore files from Vista Backup file structure
    By LokaPujya in forum Windows Vista Performance
    Replies: 4
    Last Post: 24-08-2009, 08:38 PM
  5. File System Structure Corrupt?
    By NRC Help in forum Windows Server Help
    Replies: 6
    Last Post: 25-10-2007, 04:58 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,631,765.92371 seconds with 17 queries