[root@vtl ~]# xfs_repair -n /dev/vg_amanda/backups

Phase 1 - find and verify superblock...

Phase 2 - using internal log

        - scan filesystem freespace and inode maps...

agf_freeblks 237913703, counted 235702238 in ag 0

agf_longest 237769157, counted 225943813 in ag 0

agi_count 1920, counted 2240 in ag 0

agi_freecount 1, counted 19 in ag 0

sb_ifree 246, counted 278

sb_fdblocks 1269285644, counted 1269057275

        - found root inode chunk

Phase 3 - for each AG...

        - scan (but don't clear) agi unlinked lists...

        - process known inodes and perform inode discovery...

        - agno = 0

bad directory block magic # 0x58443244 in block 0 for directory inode 157

data fork in inode 159 claims metadata block 16

bad data fork in inode 159

would have cleared inode 159

data fork in regular inode 161 claims used block 15

bad data fork in inode 161

would have cleared inode 161

bad directory block magic # 0x58443244 in block 0 for directory inode 1402283

corrupt block 0 in directory inode 1402283

        would junk block

no . entry for directory 1402283

no .. entry for directory 1402283

problem with directory contents in inode 1402283

would have cleared inode 1402283

data fork in regular inode 1402288 claims used block 92716

bad data fork in inode 1402288

would have cleared inode 1402288

data fork in ino 1402294 claims free block 94164

data fork in ino 1402294 claims free block 94165

data fork in regular inode 1448527 claims used block 92048

bad data fork in inode 1448527

would have cleared inode 1448527

data fork in regular inode 1448537 claims used block 92544

bad data fork in inode 1448537

would have cleared inode 1448537

data fork in regular inode 1448539 claims used block 92560

bad data fork in inode 1448539

would have cleared inode 1448539

data fork in regular inode 1448541 claims used block 92576

bad data fork in inode 1448541

would have cleared inode 1448541

data fork in regular inode 1448543 claims used block 92592

bad data fork in inode 1448543

would have cleared inode 1448543

data fork in regular inode 1448545 claims used block 92608

bad data fork in inode 1448545

would have cleared inode 1448545

data fork in regular inode 1448547 claims used block 92624

bad data fork in inode 1448547

would have cleared inode 1448547

data fork in regular inode 1448549 claims used block 92632

bad data fork in inode 1448549

would have cleared inode 1448549

data fork in regular inode 1448552 claims used block 92640

bad data fork in inode 1448552

would have cleared inode 1448552

data fork in regular inode 1448554 claims used block 92641

bad data fork in inode 1448554

would have cleared inode 1448554

data fork in regular inode 1448556 claims used block 92642

bad data fork in inode 1448556

would have cleared inode 1448556

data fork in regular inode 1448558 claims used block 92643

bad data fork in inode 1448558

would have cleared inode 1448558

data fork in regular inode 1448560 claims used block 92644

bad data fork in inode 1448560

would have cleared inode 1448560

data fork in regular inode 1448562 claims used block 92645

bad data fork in inode 1448562

would have cleared inode 1448562

data fork in regular inode 1448564 claims used block 92646

bad data fork in inode 1448564

would have cleared inode 1448564

data fork in regular inode 1448566 claims used block 92647

bad data fork in inode 1448566

would have cleared inode 1448566

data fork in regular inode 1448568 claims used block 92648

bad data fork in inode 1448568

would have cleared inode 1448568

data fork in regular inode 1448569 claims used block 92649

bad data fork in inode 1448569

would have cleared inode 1448569

data fork in regular inode 1448570 claims used block 92665

bad data fork in inode 1448570

would have cleared inode 1448570

data fork in regular inode 1448571 claims used block 92666

bad data fork in inode 1448571

would have cleared inode 1448571

data fork in regular inode 1448572 claims used block 92682

bad data fork in inode 1448572

would have cleared inode 1448572

data fork in regular inode 1448573 claims used block 92683

bad data fork in inode 1448573

would have cleared inode 1448573

data fork in regular inode 1448574 claims used block 92699

bad data fork in inode 1448574

would have cleared inode 1448574

data fork in regular inode 1448575 claims used block 92700

bad data fork in inode 1448575

would have cleared inode 1448575

data fork in ino 1507554 claims free block 219741

data fork in ino 1507570 claims free block 266948

data fork in regular inode 1507603 claims used block 94220

bad data fork in inode 1507603

would have cleared inode 1507603

data fork in regular inode 1507606 claims used block 94193

bad data fork in inode 1507606

would have cleared inode 1507606

data fork in regular inode 1507607 claims used block 94194

bad data fork in inode 1507607

would have cleared inode 1507607

data fork in regular inode 1507608 claims used block 94210

bad data fork in inode 1507608

would have cleared inode 1507608

data fork in regular inode 1507609 claims used block 94211

bad data fork in inode 1507609

would have cleared inode 1507609

data fork in regular inode 1507610 claims used block 94219

bad data fork in inode 1507610

would have cleared inode 1507610

data fork in regular inode 1507611 claims used block 92039

bad data fork in inode 1507611

would have cleared inode 1507611

data fork in regular inode 1507612 claims used block 94221

bad data fork in inode 1507612

would have cleared inode 1507612

data fork in regular inode 1507615 claims used block 92047

bad data fork in inode 1507615

would have cleared inode 1507615

data fork in ino 234233037 claims free block 16355169

data fork in regular inode 234233038 claims used block 14640189

bad data fork in inode 234233038

would have cleared inode 234233038

data fork in regular inode 234233039 claims used block 14640190

bad data fork in inode 234233039

would have cleared inode 234233039

data fork in regular inode 234233040 claims used block 14640198

bad data fork in inode 234233040

would have cleared inode 234233040

data fork in regular inode 234233041 claims used block 14640199

bad data fork in inode 234233041

would have cleared inode 234233041

data fork in regular inode 234233042 claims used block 15688759

bad data fork in inode 234233042

would have cleared inode 234233042

data fork in regular inode 234233043 claims used block 15688760

bad data fork in inode 234233043

would have cleared inode 234233043

data fork in regular inode 234233044 claims used block 16213032

bad data fork in inode 234233044

would have cleared inode 234233044

data fork in regular inode 234233045 claims used block 16213033

bad data fork in inode 234233045

would have cleared inode 234233045

imap claims a free inode 261505823 is in use, would correct imap and clear inode

        - agno = 1

        - agno = 2

        - agno = 3

        - agno = 4

        - agno = 5

        - process newly discovered inodes...

Phase 4 - check for duplicate blocks...

        - setting up duplicate extent list...

        - check for inodes claiming duplicate blocks...

        - agno = 0

        - agno = 3

        - agno = 1

entry "00001-soa22._opt.0" at block 0 offset 264 in directory inode 145 references free inode 159

        would clear inode number in entry at offset 264...

entry "00002-soa22._etc.0" at block 0 offset 408 in directory inode 145 references free inode 161

        would clear inode number in entry at offset 408...

        - agno = 4

        - agno = 5

        - agno = 2

entry "00000-apache-oechsle-1" at block 0 offset 96 in directory inode 155 references free inode 234233045

        would clear inode number in entry at offset 96...

bad directory block magic # 0x58443244 in block 0 for directory inode 157

data fork in ino 158 claims dup extent, off - 0, start - 15, cnt 1

bad data fork in inode 158

would have cleared inode 158

imap claims in-use inode 159 is free, would correct imap

data fork in ino 161 claims dup extent, off - 0, start - 15, cnt 1

bad data fork in inode 161

would have cleared inode 161

data fork in regular inode 162 claims used block 20

would have cleared inode 162

data fork in ino 175 claims dup extent, off - 0, start - 92716, cnt 8

bad data fork in inode 175

would have cleared inode 175

inode block 16 multiply claimed, state was 3

inode block 17 multiply claimed, state was 3

inode block 18 multiply claimed, state was 3

data fork in ino 298 claims dup extent, off - 0, start - 92724, cnt 1

bad data fork in inode 298

would have cleared inode 298

inode block 19 multiply claimed, state was 3

entry "00004-ftp._var_spool_cron.0" at block 0 offset 704 in directory inode 327322 references free inode 1402288

        would clear inode number in entry at offset 704...

entry "00004-ftpsmu._var_spool_cron.0" at block 0 offset 712 in directory inode 327343 references free inode 1507606

        would clear inode number in entry at offset 712...

entry "00004.ftpsmu._var_spool_cron.0" at block 0 offset 816 in directory inode 327343 references free inode 1507607

        would clear inode number in entry at offset 816...

entry "00005-TAPEEND" at block 0 offset 896 in directory inode 327343 references free inode 1507608

        would clear inode number in entry at offset 896...

entry "00005.TAPEEND" at block 0 offset 952 in directory inode 327343 references free inode 1507609

        would clear inode number in entry at offset 952...

entry "info" in shortform directory 327356 references free inode 1507610

would have junked entry "info" in directory inode 327356

entry "00000-ftpmq-hites-1" at block 0 offset 88 in directory inode 1402240 references free inode 1507603

        would clear inode number in entry at offset 88...

entry "00000.ftpmq-hites-1" at block 0 offset 160 in directory inode 1402240 references free inode 1507611

        would clear inode number in entry at offset 160...

entry "00001-ftpmqhites._home.0" at block 0 offset 240 in directory inode 1402240 references free inode 1507612

        would clear inode number in entry at offset 240...

entry "00002-ftpmqhites._etc.0" at block 0 offset 416 in directory inode 1402240 references free inode 1507615

        would clear inode number in entry at offset 416...

bad directory block magic # 0x58443244 in block 0 for directory inode 1402283

corrupt block 0 in directory inode 1402283

        would junk block

no . entry for directory 1402283

no .. entry for directory 1402283

problem with directory contents in inode 1402283

would have cleared inode 1402283

data fork in ino 1402288 claims dup extent, off - 0, start - 90665, cnt 2064

bad data fork in inode 1402288

would have cleared inode 1402288

data fork in ino 1402294 claims dup extent, off - 0, start - 94156, cnt 40

bad data fork in inode 1402294

would have cleared inode 1402294

data fork in ino 1402295 claims dup extent, off - 0, start - 94196, cnt 1

bad data fork in inode 1402295

would have cleared inode 1402295

data fork in ino 1402296 claims dup extent, off - 0, start - 94197, cnt 16

bad data fork in inode 1402296

would have cleared inode 1402296

data fork in ino 1402297 claims dup extent, off - 0, start - 94213, cnt 1

bad data fork in inode 1402297

would have cleared inode 1402297

data fork in ino 1402298 claims dup extent, off - 0, start - 94214, cnt 8

bad data fork in inode 1402298

would have cleared inode 1402298

data fork in ino 1448527 claims dup extent, off - 0, start - 92048, cnt 496

bad data fork in inode 1448527

would have cleared inode 1448527

data fork in ino 1448537 claims dup extent, off - 0, start - 92544, cnt 16

bad data fork in inode 1448537

would have cleared inode 1448537

data fork in ino 1448539 claims dup extent, off - 0, start - 92560, cnt 16

bad data fork in inode 1448539

would have cleared inode 1448539

data fork in ino 1448541 claims dup extent, off - 0, start - 92576, cnt 16

bad data fork in inode 1448541

would have cleared inode 1448541

data fork in ino 1448543 claims dup extent, off - 0, start - 92592, cnt 16

bad data fork in inode 1448543

would have cleared inode 1448543

data fork in ino 1448545 claims dup extent, off - 0, start - 92608, cnt 16

bad data fork in inode 1448545

would have cleared inode 1448545

data fork in ino 1448547 claims dup extent, off - 0, start - 92624, cnt 8

bad data fork in inode 1448547

would have cleared inode 1448547

data fork in ino 1448549 claims dup extent, off - 0, start - 92632, cnt 8

bad data fork in inode 1448549

would have cleared inode 1448549

data fork in ino 1448552 claims dup extent, off - 0, start - 92640, cnt 1

bad data fork in inode 1448552

would have cleared inode 1448552

data fork in ino 1448554 claims dup extent, off - 0, start - 92641, cnt 1

bad data fork in inode 1448554

would have cleared inode 1448554

data fork in ino 1448556 claims dup extent, off - 0, start - 92642, cnt 1

bad data fork in inode 1448556

would have cleared inode 1448556

data fork in ino 1448558 claims dup extent, off - 0, start - 92643, cnt 1

bad data fork in inode 1448558

would have cleared inode 1448558

data fork in ino 1448560 claims dup extent, off - 0, start - 92644, cnt 1

bad data fork in inode 1448560

would have cleared inode 1448560

data fork in ino 1448562 claims dup extent, off - 0, start - 92645, cnt 1

bad data fork in inode 1448562

would have cleared inode 1448562

data fork in ino 1448564 claims dup extent, off - 0, start - 92646, cnt 1

bad data fork in inode 1448564

would have cleared inode 1448564

data fork in ino 1448566 claims dup extent, off - 0, start - 92647, cnt 1

bad data fork in inode 1448566

would have cleared inode 1448566

data fork in ino 1448568 claims dup extent, off - 0, start - 92648, cnt 1

bad data fork in inode 1448568

would have cleared inode 1448568

data fork in ino 1448569 claims dup extent, off - 0, start - 92649, cnt 16

bad data fork in inode 1448569

would have cleared inode 1448569

data fork in ino 1448570 claims dup extent, off - 0, start - 92665, cnt 1

bad data fork in inode 1448570

would have cleared inode 1448570

data fork in ino 1448571 claims dup extent, off - 0, start - 92666, cnt 16

bad data fork in inode 1448571

would have cleared inode 1448571

data fork in ino 1448572 claims dup extent, off - 0, start - 92682, cnt 1

bad data fork in inode 1448572

would have cleared inode 1448572

data fork in ino 1448573 claims dup extent, off - 0, start - 92683, cnt 16

bad data fork in inode 1448573

would have cleared inode 1448573

data fork in ino 1448574 claims dup extent, off - 0, start - 92699, cnt 1

entry "slot2" in shortform directory 17184025986 references free inode 1402283

bad data fork in inode 1448574

would have junked entry "slot2" in directory inode 17184025986

would have cleared inode 1448574

data fork in ino 1448575 claims dup extent, off - 0, start - 92700, cnt 16

bad data fork in inode 1448575

would have cleared inode 1448575

data fork in ino 1507603 claims dup extent, off - 0, start - 94220, cnt 1

bad data fork in inode 1507603

would have cleared inode 1507603

data fork in ino 1507606 claims dup extent, off - 0, start - 94193, cnt 1

bad data fork in inode 1507606

would have cleared inode 1507606

data fork in ino 1507607 claims dup extent, off - 0, start - 94194, cnt 16

bad data fork in inode 1507607

would have cleared inode 1507607

data fork in ino 1507608 claims dup extent, off - 0, start - 94210, cnt 1

bad data fork in inode 1507608

would have cleared inode 1507608

data fork in ino 1507609 claims dup extent, off - 0, start - 94211, cnt 8

bad data fork in inode 1507609

would have cleared inode 1507609

data fork in ino 1507610 claims dup extent, off - 0, start - 94219, cnt 1

bad data fork in inode 1507610

would have cleared inode 1507610

data fork in ino 1507611 claims dup extent, off - 0, start - 92039, cnt 8

bad data fork in inode 1507611

would have cleared inode 1507611

data fork in ino 1507612 claims dup extent, off - 0, start - 94221, cnt 1

bad data fork in inode 1507612

would have cleared inode 1507612

data fork in ino 1507615 claims dup extent, off - 0, start - 92047, cnt 1

bad data fork in inode 1507615

would have cleared inode 1507615

entry "slot2" in shortform directory 17184068706 references free inode 234233043

would have junked entry "slot2" in directory inode 17184068706

entry "00000.jboss-superco-2" at block 0 offset 160 in directory inode 17305802 references free inode 1448549

        would clear inode number in entry at offset 160...

entry "00002-superco21._opt.0" at block 0 offset 528 in directory inode 17305802 references free inode 1448552

        would clear inode number in entry at offset 528...

entry "00003-superco22._opt.0" at block 0 offset 704 in directory inode 17305802 references free inode 1448554

        would clear inode number in entry at offset 704...

entry "00004-superco24._etc.0" at block 0 offset 880 in directory inode 17305802 references free inode 1448556

        would clear inode number in entry at offset 880...

entry "00005-superco21._etc.0" at block 0 offset 1056 in directory inode 17305802 references free inode 1448558

        would clear inode number in entry at offset 1056...

entry "00006-superco22._etc.0" at block 0 offset 1232 in directory inode 17305802 references free inode 1448560

        would clear inode number in entry at offset 1232...

entry "00007-superco21._usr_local.0" at block 0 offset 1408 in directory inode 17305802 references free inode 1448562

        would clear inode number in entry at offset 1408...

entry "00008-superco22._usr_local.0" at block 0 offset 1584 in directory inode 17305802 references free inode 1448564

        would clear inode number in entry at offset 1584...

entry "00009-superco24._usr_local.0" at block 0 offset 1760 in directory inode 17305802 references free inode 1448566

        would clear inode number in entry at offset 1760...

entry "00010-superco21._b2b.0" at block 0 offset 1936 in directory inode 17305802 references free inode 1448568

        would clear inode number in entry at offset 1936...

entry "00010.superco21._b2b.0" at block 0 offset 2024 in directory inode 17305802 references free inode 1448569

        would clear inode number in entry at offset 2024...

entry "00011-superco22._b2b.0" at block 0 offset 2112 in directory inode 17305802 references free inode 1448570

        would clear inode number in entry at offset 2112...

entry "00011.superco22._b2b.0" at block 0 offset 2200 in directory inode 17305802 references free inode 1448571

        would clear inode number in entry at offset 2200...

entry "00012-superco24._b2b.0" at block 0 offset 2288 in directory inode 17305802 references free inode 1448572

        would clear inode number in entry at offset 2288...

entry "00012.superco24._b2b.0" at block 0 offset 2376 in directory inode 17305802 references free inode 1448573

        would clear inode number in entry at offset 2376...

entry "00013-superco21._LOGS__B2B.0" at block 0 offset 2464 in directory inode 17305802 references free inode 1448574

        would clear inode number in entry at offset 2464...

entry "00013.superco21._LOGS__B2B.0" at block 0 offset 2552 in directory inode 17305802 references free inode 1448575

        would clear inode number in entry at offset 2552...

entry "00027.inkaf24._var_spool_cron.0" at block 0 offset 1176 in directory inode 37895943 references free inode 1448541

        would clear inode number in entry at offset 1176...

entry "00030.TAPEEND" at block 0 offset 2712 in directory inode 37895943 references free inode 1448547

        would clear inode number in entry at offset 2712...

entry "00020.inkaf21._LOGS__B2B.0" at block 0 offset 3288 in directory inode 37895943 references free inode 1448527

        would clear inode number in entry at offset 3288...

entry "00025.inkaf22._var_spool_cron.0" at block 1 offset 72 in directory inode 37895943 references free inode 1448537

        would clear inode number in entry at offset 72...

entry "00026.inkaf25._var_spool_cron.0" at block 1 offset 280 in directory inode 37895943 references free inode 1448539

        would clear inode number in entry at offset 280...

entry "00028.inkaf23._var_spool_cron.0" at block 1 offset 488 in directory inode 37895943 references free inode 1448543

        would clear inode number in entry at offset 488...

entry "00029.inkaf21._var_spool_cron.0" at block 1 offset 696 in directory inode 37895943 references free inode 1448545

        would clear inode number in entry at offset 696...

data fork in ino 208375216 claims dup extent, off - 0, start - 14640189, cnt 1048560

bad data fork in inode 208375216

would have cleared inode 208375216

entry "00002.samba._samba-usuarios_trabajo_Proyectos.0" at block 0 offset 608 in directory inode 234232915 references free inode 208375216

        would clear inode number in entry at offset 608...

entry "00005-samba._samba-usuarios_trabajo_Proyectos_AUDITA__MENSUALES.0" at block 0 offset 1336 in directory inode 234232915 references free inode 234233038

        would clear inode number in entry at offset 1336...

entry "00005.samba._samba-usuarios_trabajo_Proyectos_AUDITA__MENSUALES.0" at block 0 offset 1504 in directory inode 234232915 references free inode 234233039

        would clear inode number in entry at offset 1504...

entry "00006-TAPEEND" at block 0 offset 1616 in directory inode 234232915 references free inode 234233040

        would clear inode number in entry at offset 1616...

entry "00006.TAPEEND" at block 0 offset 1672 in directory inode 234232915 references free inode 234233041

        would clear inode number in entry at offset 1672...

entry "git" at block 0 offset 48 in directory inode 234233037 references free inode 17452451465

        would clear inode number in entry at offset 48...

entry "git_20140926.tar.gz" at block 0 offset 104 in directory inode 234233037 references free inode 261505818

        would clear inode number in entry at offset 104...

entry "git_20141003.tar.gz" at block 0 offset 176 in directory inode 234233037 references free inode 261505819

        would clear inode number in entry at offset 176...

entry "git_20141010.tar.gz" at block 0 offset 248 in directory inode 234233037 references free inode 261505820

        would clear inode number in entry at offset 248...

entry "git_20141017.tar.gz" at block 0 offset 320 in directory inode 234233037 references free inode 261505821

        would clear inode number in entry at offset 320...

entry "git_20141024.tar.gz" at block 0 offset 392 in directory inode 234233037 references free inode 261505822

        would clear inode number in entry at offset 392...

entry "git_20141114.tar.gz" at block 0 offset 608 in directory inode 234233037 references free inode 234233042

        would clear inode number in entry at offset 608...

data fork in ino 234233038 claims dup extent, off - 0, start - 14640189, cnt 1

bad data fork in inode 234233038

would have cleared inode 234233038

imap claims in-use inode 234233039 is free, would correct imap

imap claims in-use inode 234233040 is free, would correct imap

data fork in regular inode 234233041 claims used block 15688749

would have cleared inode 234233041

data fork in regular inode 234233042 claims used block 15688759

would have cleared inode 234233042

data fork in regular inode 234233043 claims used block 15688760

would have cleared inode 234233043

data fork in regular inode 234233044 claims used block 16213032

would have cleared inode 234233044

data fork in regular inode 234233045 claims used block 16213033

would have cleared inode 234233045

No modify flag set, skipping phase 5

Phase 6 - check inode connectivity...

        - traversing filesystem ...

entry "00000.activemq-soabbr-4" in directory inode 145 points to free inode 158, would junk entry

entry "00002-soa22._etc.0" in directory inode 145 points to free inode 161, would junk entry

entry "00002.soa22._etc.0" in directory inode 145 points to free inode 162, would junk entry

bad hash table for directory inode 145 (no data entry): would rebuild

entry "00000-apache-oechsle-1" in directory inode 155 points to free inode 234233045, would junk entry

entry "00000.apache-oechsle-1" in directory inode 155 points to free inode 175, would junk entry

entry "00001-TAPEEND" in directory inode 155 points to free inode 298, would junk entry

bad hash table for directory inode 155 (no data entry): would rebuild

bad directory block magic # 0x58443244 for directory inode 157 block 0: would fix magic # to 0x58443242

bad hash table for directory inode 157 (no data entry): would rebuild

entry "00004-ftp._var_spool_cron.0" in directory inode 327322 points to free inode 1402288, would junk entry

entry "00005-TAPEEND" in directory inode 327322 points to free inode 1402294, would junk entry

entry "00005.TAPEEND" in directory inode 327322 points to free inode 1402295, would junk entry

bad hash table for directory inode 327322 (no data entry): would rebuild

entry "00000.ftp-ifh-3" in shortform directory inode 327340 points to free inode 1402296would junk entry

entry "00001.ftpifh._usr_local.0" in shortform directory inode 327340 points to free inode 1402297would junk entry

entry "00002.ftpifh._var_spool_cron.0" in shortform directory inode 327340 points to free inode 1402298would junk entry

entry "00004-ftpsmu._var_spool_cron.0" in directory inode 327343 points to free inode 1507606, would junk entry

entry "00004.ftpsmu._var_spool_cron.0" in directory inode 327343 points to free inode 1507607, would junk entry

entry "00005-TAPEEND" in directory inode 327343 points to free inode 1507608, would junk entry

entry "00005.TAPEEND" in directory inode 327343 points to free inode 1507609, would junk entry

bad hash table for directory inode 327343 (no data entry): would rebuild

entry "info" in shortform directory inode 327356 points to free inode 1507610would junk entry

entry "00000-ftpmq-hites-1" in directory inode 1402240 points to free inode 1507603, would junk entry

entry "00000.ftpmq-hites-1" in directory inode 1402240 points to free inode 1507611, would junk entry

entry "00001-ftpmqhites._home.0" in directory inode 1402240 points to free inode 1507612, would junk entry

entry "00002-ftpmqhites._etc.0" in directory inode 1402240 points to free inode 1507615, would junk entry

bad hash table for directory inode 1402240 (no data entry): would rebuild

entry "00000.jboss-superco-2" in directory inode 17305802 points to free inode 1448549, would junk entry

entry "00002-superco21._opt.0" in directory inode 17305802 points to free inode 1448552, would junk entry

entry "00003-superco22._opt.0" in directory inode 17305802 points to free inode 1448554, would junk entry

entry "00004-superco24._etc.0" in directory inode 17305802 points to free inode 1448556, would junk entry

entry "00005-superco21._etc.0" in directory inode 17305802 points to free inode 1448558, would junk entry

entry "00006-superco22._etc.0" in directory inode 17305802 points to free inode 1448560, would junk entry

entry "00007-superco21._usr_local.0" in directory inode 17305802 points to free inode 1448562, would junk entry

entry "00008-superco22._usr_local.0" in directory inode 17305802 points to free inode 1448564, would junk entry

entry "00009-superco24._usr_local.0" in directory inode 17305802 points to free inode 1448566, would junk entry

entry "00010-superco21._b2b.0" in directory inode 17305802 points to free inode 1448568, would junk entry

entry "00010.superco21._b2b.0" in directory inode 17305802 points to free inode 1448569, would junk entry

entry "00011-superco22._b2b.0" in directory inode 17305802 points to free inode 1448570, would junk entry

entry "00011.superco22._b2b.0" in directory inode 17305802 points to free inode 1448571, would junk entry

entry "00012-superco24._b2b.0" in directory inode 17305802 points to free inode 1448572, would junk entry

entry "00012.superco24._b2b.0" in directory inode 17305802 points to free inode 1448573, would junk entry

entry "00013-superco21._LOGS__B2B.0" in directory inode 17305802 points to free inode 1448574, would junk entry

entry "00013.superco21._LOGS__B2B.0" in directory inode 17305802 points to free inode 1448575, would junk entry

bad hash table for directory inode 17305802 (no data entry): would rebuild

entry "00027.inkaf24._var_spool_cron.0" in directory inode 37895943 points to free inode 1448541, would junk entry

entry "00030.TAPEEND" in directory inode 37895943 points to free inode 1448547, would junk entry

entry "00020.inkaf21._LOGS__B2B.0" in directory inode 37895943 points to free inode 1448527, would junk entry

entry "00025.inkaf22._var_spool_cron.0" in directory inode 37895943 points to free inode 1448537, would junk entry

entry "00026.inkaf25._var_spool_cron.0" in directory inode 37895943 points to free inode 1448539, would junk entry

entry "00028.inkaf23._var_spool_cron.0" in directory inode 37895943 points to free inode 1448543, would junk entry

entry "00029.inkaf21._var_spool_cron.0" in directory inode 37895943 points to free inode 1448545, would junk entry

bad hash table for directory inode 37895943 (no data entry): would rebuild

entry "00002.samba._samba-usuarios_trabajo_Proyectos.0" in directory inode 234232915 points to free inode 208375216, would junk entry

entry "00005-samba._samba-usuarios_trabajo_Proyectos_AUDITA__MENSUALES.0" in directory inode 234232915 points to free inode 234233038, would junk entry

entry "00006.TAPEEND" in directory inode 234232915 points to free inode 234233041, would junk entry

bad hash table for directory inode 234232915 (no data entry): would rebuild

entry "git" in directory inode 234233037 points to free inode 17452451465, would junk entry

entry "git_20140926.tar.gz" in directory inode 234233037 points to free inode 261505818, would junk entry

entry "git_20141003.tar.gz" in directory inode 234233037 points to free inode 261505819, would junk entry

entry "git_20141010.tar.gz" in directory inode 234233037 points to free inode 261505820, would junk entry

entry "git_20141017.tar.gz" in directory inode 234233037 points to free inode 261505821, would junk entry

entry "git_20141024.tar.gz" in directory inode 234233037 points to free inode 261505822, would junk entry

entry "git_20141031.tar.gz" in dir inode 234233037 inconsistent with .. value (17452451463) in ino 229760502

        would clear entry "git_20141031.tar.gz"

entry "git_20141114.tar.gz" in directory inode 234233037 points to free inode 234233042, would junk entry

bad hash table for directory inode 234233037 (no data entry): would rebuild

entry "slot2" in shortform directory inode 17184025986 points to free inode 1402283would junk entry

entry "slot2" in directory inode 17184068704 not consistent with .. value (17452451463) in inode 234233037,

would junk entry

entry "slot2" in shortform directory inode 17184068706 points to free inode 234233043would junk entry

        - traversal finished ...

        - moving disconnected inodes to lost+found ...

disconnected inode 169, would move to lost+found

disconnected inode 297, would move to lost+found

disconnected inode 1507554, would move to lost+found

disconnected inode 1507604, would move to lost+found

disconnected inode 1507614, would move to lost+found

disconnected inode 8445001, would move to lost+found

disconnected inode 8445004, would move to lost+found

disconnected inode 8445005, would move to lost+found

disconnected inode 8445006, would move to lost+found

disconnected inode 8445007, would move to lost+found

disconnected inode 8445008, would move to lost+found

disconnected inode 8445009, would move to lost+found

disconnected inode 8445010, would move to lost+found

disconnected inode 8445011, would move to lost+found

disconnected inode 8445012, would move to lost+found

disconnected inode 8445013, would move to lost+found

disconnected inode 8445014, would move to lost+found

disconnected inode 8445015, would move to lost+found

disconnected inode 8445040, would move to lost+found

disconnected inode 11376352, would move to lost+found

disconnected inode 11376353, would move to lost+found

disconnected inode 11376354, would move to lost+found

disconnected inode 11376355, would move to lost+found

disconnected inode 11376356, would move to lost+found

disconnected inode 11376357, would move to lost+found

disconnected inode 11376358, would move to lost+found

disconnected inode 11376359, would move to lost+found

disconnected inode 11376360, would move to lost+found

disconnected inode 11376361, would move to lost+found

disconnected inode 11376362, would move to lost+found

disconnected inode 11376363, would move to lost+found

disconnected inode 11376364, would move to lost+found

disconnected inode 11376365, would move to lost+found

disconnected inode 11376366, would move to lost+found

disconnected inode 11376367, would move to lost+found

disconnected inode 11376368, would move to lost+found

disconnected inode 11376369, would move to lost+found

disconnected inode 11376370, would move to lost+found

disconnected inode 11376371, would move to lost+found

disconnected inode 11376372, would move to lost+found

disconnected inode 11376373, would move to lost+found

disconnected inode 11376374, would move to lost+found

disconnected inode 11376375, would move to lost+found

disconnected inode 11376376, would move to lost+found

disconnected inode 11376377, would move to lost+found

disconnected inode 11376378, would move to lost+found

disconnected inode 11376379, would move to lost+found

disconnected inode 11376380, would move to lost+found

disconnected inode 11376381, would move to lost+found

disconnected inode 11376382, would move to lost+found

disconnected inode 11376383, would move to lost+found

disconnected inode 11376384, would move to lost+found

disconnected inode 11376385, would move to lost+found

disconnected inode 11376386, would move to lost+found

disconnected inode 11376387, would move to lost+found

disconnected inode 11376388, would move to lost+found

disconnected inode 11376389, would move to lost+found

disconnected inode 11376390, would move to lost+found

disconnected inode 11376391, would move to lost+found

disconnected inode 11376392, would move to lost+found

disconnected inode 11376393, would move to lost+found

disconnected inode 11376394, would move to lost+found

disconnected inode 11376396, would move to lost+found

disconnected inode 11376397, would move to lost+found

disconnected inode 11376398, would move to lost+found

disconnected inode 11376399, would move to lost+found

disconnected inode 11376400, would move to lost+found

disconnected inode 11376401, would move to lost+found

disconnected dir inode 234233037, would move to lost+found

disconnected inode 261759691, would move to lost+found

disconnected inode 261759696, would move to lost+found

disconnected inode 261759697, would move to lost+found

disconnected inode 261759698, would move to lost+found

disconnected dir inode 12893594611, would move to lost+found

disconnected dir inode 12898288751, would move to lost+found

disconnected dir inode 12898288752, would move to lost+found

disconnected dir inode 13162280161, would move to lost+found

disconnected dir inode 21743466509, would move to lost+found

Phase 7 - verify link counts...

would have reset inode 170 nlinks from 1 to 2

would have reset inode 1402284 nlinks from 1 to 2

would have reset inode 1507567 nlinks from 1 to 2

would have reset inode 11376410 nlinks from 1 to 2

would have reset inode 229760503 nlinks from 1 to 2

would have reset inode 234233037 nlinks from 3 to 2

would have reset inode 17184025986 nlinks from 6 to 5

would have reset inode 17184068704 nlinks from 6 to 5

would have reset inode 17184068706 nlinks from 6 to 5

No modify flag set, skipping filesystem flush and exiting.