My question deals with the relationship between the read and execute bits on a directory. I'm going to give my assumptions, first, all according to my current knowledge, then ask my question in bold in the context of those assumptions.
I recently ran rkhunter.
I found out the inode information of the most important directory of my server was corrupted, and I couldn't access its files.
My file system is EXT3
I tried fsck on the image of partition, no success.
I tried dd_rhelp, it doesn't any effect.
I tried debugfs , run rdump corrupted-inode-dir native-dir , but it doesn't work without any error.
How can I recover my data in this directory?
I found out the inode information of the most important directory of my server was corrupted, and I couldn't access its files.
My file system is EXT3
I tried fsck on the image of partition, no success.
I tried dd_rhelp, it doesn't any effect.
I tried debugfs , run rdump corrupted-inode-dir native-dir , but it doesn't work without any error.
How can I recover my data in this directory?
HOSTNAME:~ # fsck -n /FSMOUNTPOINT
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
Warning!
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]
Linux ext2 and ext3 file system area is classified into blocks, which are groups organized by category. It is of particular data structure of each group that defines and contains valuable information, call the group descriptor blocks. Data structure is assigned to each block groups to access it and even inode bitmap, inode table and block bitmap of location information.
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.
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.
Email this page
