> unfortunately I need more that just the set of blocked tasks to diagnose the > problem. If you could get the result of > echo t > /proc/sysrq-trigger > that might help a lot. This might be bigger than the dmesg buffer, so you > might try booting with 'log_buf_len=1M' just to be sure. > Hi Neil, Thanks for the feedback. I've stuck the sysrq-t output here: http://buttersideup.com/files/md-raid1-lockup-lvm-snapshot/iodeadlock-sysrq-t.txt ... this was soon after the io to md2 stopped - md0 seems fine... oldshoreham:~# cat /proc/mdstat Personalities : [raid1] md2 : active raid1 sda6[0] sdb6[1] 404600128 blocks [2/2] [UU] [>....................] resync = 0.1% (437056/404600128) finish=343321.2min speed=19K/sec ... I also tried an older Debian 5.0.x kernel from Mar 2009, which is a less-patched 2.6.26, and got the same results. 2.6.32 hasn't deadlocked after 10 minutes (2.6.26 usually does within a minute of boot-up), so I'll leave it re-syncing overnight... Cheers! Tim. -- South East Open Source Solutions Limited Registered in England and Wales with company number 06134732. Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309 -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
