When accessing a file path corresponding to a binded mount point, Darshan is unable to recognize the actual underlying mount point it references. This prevents Darshan from determining the underlying file system type, which is necessary for determining the FS block size (which is used to determine whether I/O access are aligned or not).

It would be nice if Darshan could recognize binded mount points and store mappings from these bind mount points to the true underlying mount point in its runtime data structures. When an application accesses files in the binded mount point, Darshan can map them to the actual mount points it stores in the log file and correctly determine the underlying FS type and block size.