On Mon, Jul 15, 2013 at 06:09:03PM +0200, Felipe Monteiro de Carvalho wrote: > Hello, > > Thanks. Now I think that I am getting closer to something more concrete. > > My superblock says: > > superblock^.s_blocks_per_group = 32768 > superblock^.s_inodes_per_group = 8080 > superblock^.s_log_block_size = 2 -> so each block has 4k bytes > > And when reading the root "/" I obtain the following information for > the directory /bin/ : inode=8081 > > So I calculate that it should have: > groupnr=1 (because it is above 8080 inodes per group) > offset for groupnr 1 --> 4k * 32768 = 0x8000000 > > But I have utilized a hex editor (oh boy, it was hard to find one that > would read files over 4GB....) And the directory listing of /bin/ is > located in aprox. near 0x21B0000 > > As if each block group would have a size of 0x2000000 .... but this > size would be valid I would expect if > superblock^.s_blocks_per_group=8192 ... > > Any idea what I missed here that the calculations went wrong? You're forgetting to read the inode structure. So take the inode number, determine that it's in the inode table fragment which belongs to block group #1, then look up in the block group descriptors the starting block of the inode table for bg #1, then look up the inode size in the superblock, to determine the block number and offset to read the inode structure. Then you need to look at the inode structure to map logical block #0, to the physical block number where the directory entries are located. I suggest you RTFS in libext2fs.... - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
