> Hi,
>
> Here is what I have done. I might have been stupic :|
>
Well, your rsync appears to have died in the socket code, not xfs....
I am not sure we can help with that one.
> 4) I umount both filesystems and run xfs_repair -n on them
>
> #xfs_repair -n /dev/md0
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - scan filesystem freespace and inode maps...
> - 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
> - agno = 1
> <...>
> - agno = 107
> - process newly discovered inodes...
> Phase 4 - check for duplicate blocks...
> - setting up duplicate extent list...
> - check for inodes claiming duplicate blocks...
> - agno = 0
> <...>
> - agno = 107
> No modify flag set, skipping phase 5
> Phase 6 - check inode connectivity...
> - traversing filesystem starting at / ...
> - traversal finished ...
> - traversing all unattached subtrees ...
> - traversals finished ...
> - moving disconnected inodes to lost+found ...
> Phase 7 - verify link counts...
> No modify flag set, skipping filesystem flush and exiting.
>
> # xfs_repair -n /dev/sda1
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - scan filesystem freespace and inode maps...
> - 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
> <...>
> - agno = 17
> - process newly discovered inodes...
> Phase 4 - check for duplicate blocks...
> - setting up duplicate extent list...
> - check for inodes claiming duplicate blocks...
> - agno = 0
> <...>
> - agno = 17
> No modify flag set, skipping phase 5
> Phase 6 - check inode connectivity...
> - traversing filesystem starting at / ...
> - traversal finished ...
> - traversing all unattached subtrees ...
> - traversals finished ...
> - moving disconnected inodes to lost+found ...
> Phase 7 - verify link counts...
> No modify flag set, skipping filesystem flush and exiting.
>
> 5) I could remount the plain xfs partition but not the raid5 array:(
> # mount /raid5/
> mount: wrong fs type, bad option, bad superblock on /dev/md0,
> or too many mounted file systems
>
> on the syslog file:
> Jul 19 20:16:56 nfs kernel: XFS: xlog_recover_reorder_trans:
> unrecognized type of log
> operation
This error means it found something in the log which is could not
understand. If you had actually run repair without the -n option
then it would have zeroed out the log and you would never have
seen this, that may be your only way of mounting the filesystem
from here, however before you do so, could you run:
xfs_logprint -t -b -i /dev/md0
if it core dumps try adding the -e option.
and
xfs_check /dev/md0
and send me the output.
Steve
>
>
>
> Any idea what are the next steps?
>
> Regards,
>
> Tru
> --
> Dr Tru Huynh | Bioinformatique Structurale
> mailto:tru@xxxxxxxxxx | tel/fax +33 1 45 68 87 37/19
> Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France
|