1Backing up journal inode block information. 2 3Pass 1: Checking inodes, blocks, and sizes 4HTREE directory inode 13345 has an invalid root node. 5Clear HTree index? yes 6 7HTREE directory inode 26689 has an unsupported hash version (240) 8Clear HTree index? yes 9 10HTREE directory inode 40033 has an invalid root node. 11Clear HTree index? yes 12 13HTREE directory inode 53377 has a tree depth (8) which is too big 14Clear HTree index? yes 15 16HTREE directory inode 66721 uses an incompatible htree root node flag. 17Clear HTree index? yes 18 19Pass 2: Checking directory structure 20Problem in HTREE directory inode 80065: node (0) has an unordered hash table 21Clear HTree index? yes 22 23Problem in HTREE directory inode 86737: node (0) has invalid limit (511) 24Clear HTree index? yes 25 26Problem in HTREE directory inode 93409: node (0) has invalid count (234) 27Clear HTree index? yes 28 29Problem in HTREE directory inode 73393: node (1) has bad min hash 30Problem in HTREE directory inode 73393: node (2) has bad max hash 31Invalid HTREE directory inode 73393 (/test6). Clear HTree index? yes 32 33Pass 3: Checking directory connectivity 34Pass 3A: Optimizing directories 35Pass 4: Checking reference counts 36Pass 5: Checking group summary information 37 38test_filesys: ***** FILE SYSTEM WAS MODIFIED ***** 39test_filesys: 1921/100080 files (0.0% non-contiguous), 13642/15361 blocks 40Exit status is 1 41