Abstract: A request is received to copy a file from a source to a target in a file system. The source is associated with a source inode, and the target is associated with a target inode. A list is generated of the one of the source or target inodes followed by another of the source or target inodes according to inode numbers identifying the source and target inodes. A first determination includes determining that the one inode is the source inode and the other inode is the target inode. When the first determination is made, a read rename lock is acquired for the source inode, followed by a write rename lock for the target inode, followed by a read inode lock for the source inode, followed by a write inode lock for the target inode. After the locks have been acquired, a chunk map of the source inode is copied to the target inode.

Abstract: A method, article of manufacture, and apparatus for analyzing a distributed file system is discussed. A metadata operation is captured in an audit log, wherein the metadata operation is on an object stored in the distributed file system. An event is pushed to a distributed commit log and a real-time analytics engine in response to capturing the metadata operation. The event is persistently stored in the distributed commit log.

Abstract: A request is received to copy a file from a source to a target in a file system. The source is associated with a source inode, and the target is associated with a target inode. A list is generated of the one of the source or target inodes followed by another of the source or target inodes according to inode numbers identifying the source and target inodes. A first determination includes determining that the one inode is the source inode and the other inode is the target inode. When the first determination is made, a read rename lock is acquired for the source inode, followed by a write rename lock for the target inode, followed by a read inode lock for the source inode, followed by a write inode lock for the target inode. After the locks have been acquired, a chunk map of the source inode is copied to the target inode.

Abstract: A request is received to copy a file from a source to a destination, the source being associated with a source inode, and the destination being associated with a destination inode. The source and destination inodes are sorted into a sorted order according to inode numbers identifying the source and destination inodes. Based on the sorted order, rename locks are acquired on the source and destination inodes. Based on the sorted order, inode locks are acquired on the source and destination inodes. After the rename and inode locks have been acquired, chunk map entries of the source inode are copied as entries of the destination inode to fulfill the request.