Re: Subject: [PATCH] md: avoid deadlock when raid5 array has unack badblocks during md_stop_writes.

2013-09-10 Thread y b
I use linux-next 2013-9-6 vesion and I can reproduce it when raid5 array rescovering, so sync_blockdev may not work. Some disk-controller driver handle disk error in a slowerpath, may more than 5 seconds. if shutdown or set readonly array, we can met this situation. the detail message when I met t

Re: Subject: [PATCH] md: avoid deadlock when raid5 array has unack badblocks during md_stop_writes.

2013-09-09 Thread NeilBrown
On Tue, 10 Sep 2013 13:00:52 +0800 y b wrote: > When raid5 hit a fresh badblock, this badblock will flagged as unack > badblock until md_update_sb is called. > But md_stop/reboot/md_set_readonly will avoid raid5d call md_update_sb > in md_check_recovery, the badblock will always be unack, so raid

Subject: [PATCH] md: avoid deadlock when raid5 array has unack badblocks during md_stop_writes.

2013-09-09 Thread y b
When raid5 hit a fresh badblock, this badblock will flagged as unack badblock until md_update_sb is called. But md_stop/reboot/md_set_readonly will avoid raid5d call md_update_sb in md_check_recovery, the badblock will always be unack, so raid5d thread enter a infinite loop and never can unregister