superblock

init_caches() 初始化如下几个cache： ceph_inode_cachep ceph_cap_cachep ceph_cap_flush_cachep ceph_dentry_cachep ceph_file_cachep cephfs cache ceph_mount() |__解析mount options |__创建fs client，即：struct ceph_fs_client |__创建mds client且设置fs client和mds client之间的对应关系 |__得到superblock且使用ceph_set_super()函数初始化 |__调用ceph_real_mount()函数来执行实际的mount操作 ceph_real_mount() |__若superblock中对应的s_boot为空 |__调用__ceph_open_session()函数创建client到mds的session信息 |__调用open_root_dentry()函数得到cephfs的root dentry信息 |__将root dentry写入到superblock中的s_boot中 |__若mount options中没有server path内容 |__设置当前root为supberblock对应的s_root |__调用dget(root

I know that in Unix (specifically, Mac OS X) the superblock stores information about the layout of data on the disk, including the disk addresses at which the inodes begin and end. I want to scan the list of inodes in my program to look for deleted files. How can I find the disk address at which the inodes begin? I have looked at the statfs command but it does not provide this information. Since you mention Mac OS X, let's assume you mean to do this for HFS+ only. The Wikipedia page provides some information about possible ways to start, for instance it says this about the on-disk layout:

The C language convention counts array indices from 0. Why do inode numbers start from 1 and not 0? If inode 0 is reserved is for some special use, then what is the significance of inode 0? dmeister Usually, the inode 0 is reserved because a return value of 0 usually signals an error. Multiple method in the Linux kernel -- especially in the VFS layer shared by all file systems -- return an ino_t, e.g. find_inode_number . There are more reserved inode numbers. For example in ext2 : #define EXT2_BAD_INO 1 /* Bad blocks inode */ #define EXT2_ROOT_INO 2 /* Root inode */ #define EXT2_BOOT_LOADER