This sections contains phase 1B fsck messages in the current release.
When a duplicate fragment is found in the file system, this message is displayed:
fragment DUP I=inode-number
Inode inode-number contains a fragment number fragment-number that is already claimed by the same or another inode. This error condition generates the BAD/DUP error message in phase 2. Inodes that have overlapping fragments might be determined by examining this error condition and the DUP error condition in phase 1. This is simplified by the duplicate fragment report produced at the fsck run.
When a duplicate block is found, the file system is rescanned to find the inode that previously claimed that block.