xfs_repair produces 990 error

[Libor Vanek <libor@xxxxxxxx>]

Hi,
I've had disk failure in my SW RAID, which was quite OK since it was 
only 1 of 3 disks. But system was halted so I rebooted it and afterthat 
I was unable to mount XFS system so I run xfs_repair with this result:

[root@Discobolos_2 root]# xfs_repair /dev/md0
Phase 1 - find and verify superblock...
Phase 2 - using internal log
       - zero log...
       - scan filesystem freespace and inode maps...
       - found root inode chunk
Phase 3 - for each AG...
       - scan and clear agi unlinked lists...
       - process known inodes and perform inode discovery...
       - agno = 0
       - agno = 1
       - agno = 2
       - agno = 3
       - agno = 4
       - agno = 5
       - agno = 6
       - agno = 7
       - agno = 8
       - agno = 9
       - agno = 10
       - agno = 11
no .. entry for directory 196669223
       - agno = 12
       - agno = 13
       - agno = 14
       - agno = 15
       - agno = 16
       - agno = 17
       - agno = 18
       - agno = 19
       - agno = 20
       - agno = 21
       - agno = 22
       - agno = 23
       - agno = 24
       - agno = 25
       - agno = 26
       - agno = 27
       - agno = 28
       - agno = 29
no .. entry for directory 486539427
       - agno = 30
       - agno = 31
       - agno = 32
entry contains offset out of order in shortform dir 537155859
corrected entry offsets in directory 537155859
       - agno = 33
       - agno = 34
       - agno = 35
no .. entry for directory 587629607
       - agno = 36
       - agno = 37
       - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
       - setting up duplicate extent list...
       - clear lost+found (if it exists) ...
       - clearing existing "lost+found" inode
       - deleting existing "lost+found" entry
       - check for inodes claiming duplicate blocks...
       - agno = 0
       - agno = 1
       - agno = 2
       - agno = 3
       - agno = 4
       - agno = 5
       - agno = 6
       - agno = 7
       - agno = 8
       - agno = 9
       - agno = 10
       - agno = 11
no .. entry for directory 196669223
       - agno = 12
       - agno = 13
       - agno = 14
       - agno = 15
       - agno = 16
       - agno = 17
       - agno = 18
       - agno = 19
       - agno = 20
       - agno = 21
       - agno = 22
       - agno = 23
       - agno = 24
       - agno = 25
       - agno = 26
       - agno = 27
       - agno = 28
       - agno = 29
no .. entry for directory 486539427
       - agno = 30
       - agno = 31
       - agno = 32
       - agno = 33
       - agno = 34
       - agno = 35
no .. entry for directory 587629607
       - agno = 36
       - agno = 37
Phase 5 - rebuild AG headers and trees...
       - reset superblock...
Phase 6 - check inode connectivity...
       - resetting contents of realtime bitmap and summary inodes
       - ensuring existence of lost+found directory
       - traversing filesystem starting at / ...
       - traversal finished ...
       - traversing all unattached subtrees ...
       - traversals finished ...
       - moving disconnected inodes to lost+found ...
disconnected inode 134386441, moving to lost+found
disconnected inode 134386465, moving to lost+found
disconnected inode 134386469, moving to lost+found
corrupt inode 134386469 (btree).  Unmount and run xfs_repair.
fatal error -- 990 - couldn't iget disconnected inode



Any suggestions?

Thanks a LOT,
Libor Vanek