XFS error on enbd raid1

"u.schmeling" <[email protected]>
Newsgroups gmane.linux.enbd.general
Message-ID <[email protected]>
Is there a known problem with the above combination, have some trouble 
with enbd-2.3.32, kernel 2.6.12.3.
Running a raid1 on a local disk / enbd combination. When trying to start 
a standby disk that was written by the enbd device (as part of a raid1), 
the xfs recovery wont work:
Filesystem "md6": XFS internal error xlog_valid_rec_header(1) at line 
3500 of file fs/xfs/xfs_log_recover.c.  Caller 0xf89783d5
 [<f8978198>] xlog_valid_rec_header+0x108/0x190 [xfs]
 [<f89783d5>] xlog_do_recovery_pass+0x1b5/0xb80 [xfs]
 [<f89783d5>] xlog_do_recovery_pass+0x1b5/0xb80 [xfs]
 [<c0119d2e>] __wake_up+0x3e/0x60
 [<f8978e13>] xlog_do_log_recovery+0x73/0xe0 [xfs]
 [<f8978ebb>] xlog_do_recover+0x3b/0x180 [xfs]
 [<f89790ee>] xlog_recover+0xee/0x100 [xfs]
 [<f89704de>] xlog_alloc_log+0x25e/0x330 [xfs]
 [<f896f6ad>] xfs_log_mount+0x9d/0x130 [xfs]
 [<f897aab9>] xfs_mountfs+0x909/0xea0 [xfs]
 [<f89914fa>] .text.lock.xfs_buf+0x4b/0x51 [xfs]
 [<c023acbc>] _atomic_dec_and_lock+0x2c/0x60
 [<c041980d>] _spin_unlock+0xd/0x30
 [<f8979eb8>] xfs_readsb+0x1b8/0x230 [xfs]
 [<f896acdc>] xfs_ioinit+0x1c/0x30 [xfs]
 [<f8982a7e>] xfs_mount+0x2be/0x4c0 [xfs]
 [<f89985f0>] vfs_mount+0x60/0x70 [xfs]
 [<f89985f0>] vfs_mount+0x60/0x70 [xfs]
 [<f89983de>] linvfs_fill_super+0x9e/0x210 [xfs]
 [<c023a2e7>] snprintf+0x27/0x30
 [<c01a4514>] disk_name+0xb4/0xd0
 [<c016e64e>] sb_set_blocksize+0x2e/0x60
 [<c016df99>] get_sb_bdev+0xe9/0x160
 [<f8998580>] linvfs_get_sb+0x30/0x40 [xfs]
 [<f8998340>] linvfs_fill_super+0x0/0x210 [xfs]
 [<c016e243>] do_kern_mount+0x63/0xf0
 [<c0185cae>] do_new_mount+0x9e/0x100
 [<c01863e3>] do_mount+0x193/0x1d0
 [<c01861f3>] copy_mount_options+0x63/0xc0
 [<c01867ff>] sys_mount+0x9f/0xe0
 [<c010348b>] sysenter_past_esp+0x54/0x75
XFS: log mount/recovery failed: error 990
XFS: log mount failed
regards Uwe
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.