Filesystem did not have a UUID; generating one.
Pass 1: Checking inodes, blocks, and sizes
-Inode 12 has illegal block(s). Clear? yes
+Duplicate blocks found... invoking duplicate block passes.
+Pass 1B: Rescan for duplicate/bad blocks
+Duplicate/bad block(s) in inode 12: 3 4 6
+Pass 1C: Scan directories for inodes with dup blocks.
+Pass 1D: Reconciling duplicate blocks
+(There are 1 inodes containing duplicate/bad blocks.)
-Block #1 (3) overlaps filesystem metadata in inode 12. CLEARED.
-Block #2 (4) overlaps filesystem metadata in inode 12. CLEARED.
-Block #3 (6) overlaps filesystem metadata in inode 12. CLEARED.
-Inode 12, i_size is 4096, should be 1024. Fix? yes
+File /foo (inode #12, mod time Thu Apr 28 17:57:53 1994)
+ has 3 duplicate block(s), shared with 1 file(s):
+ <filesystem metadata>
+Clone duplicate/bad blocks? yes
-Inode 12, i_blocks is 8, should be 2. Fix? yes
Pass 2: Checking directory structure
-Directory inode 12 has an unallocated block #1. Allocate? yes
+Directory inode 12, block 1, offset 0: directory corrupted
+Salvage? yes
-Directory inode 12 has an unallocated block #2. Allocate? yes
+Directory inode 12, block 2, offset 0: directory corrupted
+Salvage? yes
-Directory inode 12 has an unallocated block #3. Allocate? yes
+Directory inode 12, block 3, offset 0: directory corrupted
+Salvage? yes
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts