or updates to text file 224 in directory 210 in file system 200 as discussed above each file e g text file 216 or directory e g directory 210 may have a unique inode the inode corresponding to each file may list attributes of each user visible file and file system object e g directory within file system 200 in addition in this example it is noted that although the example directory and file structure visible to the user may be organized in a particular hierarchy the inode data associated with each file and directory may be in a single inode file 250 that may not convey the hierarchy inode file 250 may simply list the inodes as they are created or updated but the files may not be physically or logically e g as a user would u201c see u201d them in a directory listing adjacent to each other this will be discussed further in fig3 although fig2 discloses a particular number of files directories and storage resources with respect to system 200 it is understood that system 200 may have greater or fewer directories files and storage than those depicted in fig2 in addition although fig2 discloses a certain type of files with respect to system 200 the types of files in system 200 may be of any suitable type in addition although one inode file 250 is shown system 200 may have any number of inodes and or inode files system 200 may be implemented using any configuration of files or directories location in the same or geographical disparate locations in certain embodiments system 200 may be implemented by any combination of hardware and software embodied in tangible computer.