The fsck(1M) command detected duplicate blocks while checking a filesystem, so fsck(1M) is rescanning the filesystem to find the inode that originally claimed that block.
If fsck(1M) executes this optional phase, you will see additional DUP/BAD messages in phases 2 and 4.
For more information, see the chapter on checking filesystem integrity in the System Administration Guide, Volume I.