Hi,i want to know do you require only one inode to store information for a single file or you require multiple inode for storing a single fileRegardsltoso [by ltoso]
on 04/04/2010 – Made popular on 04/04/2010
I am reading about the EXT2 filesystem and I got an understanding about it. Every file system comprises of data and metadata (inode). The file system is divided into a number of blocks with 4 main blocks containing information about other blocks.
I'm trying to create a graph of the distribution of file sizes on my ext4 system. I'm trying to write a script to scrape this information from my computer somehow. I don't care where the files are stored in the directory structure, only how much space each takes up.
I am trying to understand what an inode is. However, this passage from Wikipedia puzzles me:
Installation of new libraries is simple with inode filesystems. A running process can access a library file while another process replaces that file, creating a new inode, and an all new mapping will exist for the new file so that subsequent attempts to access the library get the new version.
I am currently reading UNIX by Bach. In which I encountered a problem while reading inode section from 4th chapter where file modified time is shown as 1 :45pm and inode modified time is shown as 1:30pm.
How this is possible? Because when a file is modified, its inode is also modified so inode modification time should be the most recent time.
Today, I started thinking about inode structure passed in "open" call to device drivers in linux. I have religiously used "inode->i_rdev" for major and minor numbers before. But I never used it for any other purpose. ( Most probably I never went past my toy drivers.)
So, I was wondering if some one can explain any other usage of this structure inside device driver.
Is there any way to create a file on Solaris 10 (ZFS preferably, but UFS would be helpful as well) with a specific inode number? I need to create a file with a large inode, greater than a 32bit integer.
I am trying to test a piece of software which may be incorrectly truncating large inodes down to 32-bit numbers.