On 23.09.2012 07:59, Mikael Abrahamsson wrote: > On Sun, 23 Sep 2012, Alexander Kühn wrote: > >> root@nas:~# echo /sys/block/md*/md/sync_action >> /sys/block/md1/md/sync_action >> root@nas:~# cat /proc/mdstat >> Personalities : [raid6] [raid5] [raid4] >> md1 : active (auto-read-only) raid5 sdb[5] sdg[9] sdd[7] sdf[6] >> sde[8] sdc[2] sda[1] >> 11719408128 blocks super 1.2 level 5, 64k chunk, algorithm 2 >> [7/7] [UUUUUUU] >> bitmap: 0/15 pages [0KB], 65536KB chunk > > I'd imagine that it's the "(auto-read-only)" that is the culprit here. > If you can do something that writes to the array (mount of a > filesystem for instance) and then reproduce the problem? > Indeed, use "mdadm -w /dev/md1" to set it writeable. This immediately starts pending sync actions. In the kernel code in "drivers/md/md.c" there is the function "action_store" which handles your "sync_action" sysfs file writes. I just sets some bits in "mddev->recovery". -- 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
