Re: 4.1-rc6 radi5 OOPS
From: Neil Brown <hidden>
Date: 2015-06-11 07:02:57
Possibly related (same subject, not in this thread)
- 2015-06-13 · Re: 4.1-rc6 radi5 OOPS · Neil Brown <hidden>
- 2015-06-12 · Re: 4.1-rc6 radi5 OOPS · Jes Sorensen <hidden>
- 2015-06-10 · Re: 4.1-rc6 radi5 OOPS · Jes Sorensen <hidden>
- 2015-06-10 · Re: 4.1-rc6 radi5 OOPS · Neil Brown <hidden>
- 2015-06-10 · Re: 4.1-rc6 radi5 OOPS · Neil Brown <hidden>
On Thu, 11 Jun 2015 16:48:47 +1000 Neil Brown [off-list ref] wrote:
Would you be able to test with the following patch? There is a chance it might confirm whether two sync threads are running at the same time.
I tried the patch, and was fortunate: [ 208.626468] Register thread ffff88003cf53d00 md0_resync [ 208.629801] Started thread ffff88003cf53d00 md0_resync [ 208.629801] Finished thread ffff88003cf53d00 [ 208.639800] Reap thread ffff88003cf53d00 [ 208.639800] Finished thread ffff88003cf53d00 md0_resync [ 208.643133] Register thread ffff88003cf53700 md0_resync [ 208.643133] Reap thread (null) [ 208.646466] Started thread ffff88003cf53700 md0_resync [ 208.659799] Reap thread ffff88003cf53700 -HANG- That "(null)" is a problem - that will clear MD_RECOVERY_RUNNING, but there is a thread there. Will keep looking. NeilBrown