Linux – Does the inode data structure contains the actual address of the file on disk

Given the vast array of file systems out there, I'm certain that exceptions exist, but traditionally, the inode had an array of disk block numbers in it.

For example, in /usr/include/linux/ext3_fs.h, I see a definition of struct ext3_inode.

Inside struct ext3_inode, I see a member i_block[EXT3_N_BLOCKS];/* Pointers to blocks */

Different file systems have had different ways of keeping track of which disk blocks belong to an inode (the on-disk data structure that represents the file's data). Some have an array of block numbers, some have an array of runs or extents, a count plus the beginning block number of a run of contiguous blocks. The Berkeley FFS inode had an array of block numbers, and array of block numbers, each of those blocks contained data block numbers, and a block number that contained block numbers that contained data block numbers.

The whole thing gets a bit weirder for "log structured file systems", but those are the exception rather than the rule.

The simple answer is that what you want to do is to read the directory file, with a command like cat ., cat /etc, or cat mydir.  Of course, since this is “raw” data, you’d want to use a program that’s better suited to displaying non-ASCII data in a human-friendly way; e.g., hexdump or od.

Unfortunately, as discussed in When did directories stop being readable as files?, most versions of Unix that were released in the past two decades or so don’t allow this.  So the answer to your question may be “find a version of Unix that still allows reading directories”.  AIX, most versions of BSD, and all but the most recent versions of Solaris may qualify.  Finding a Linux that allows it may require the use of a time machine.