On 12.09.2014, at 00:24, NeilBrown <neilb@xxxxxxx> wrote: > On Fri, 12 Sep 2014 00:05:08 +0200 Marco Schindler > <marco.schindler@xxxxxxxxx> wrote: > > In that bug report you mention upgraded udev. Here you mention upgrading > mdadm.... a bit confusing. totally unsure if this is related, it may be coincidence. just found it’s odd to have a similar issue with two different processes in such a short timeframe. I have blocked >sys-fs/udev-212 and >sys-fs/mdadm-3.2 for now to give drives some rest. > Can you use "blktrace" to gather details on exactly what is being read and > when, and hopefully which process is doing it? > > Is "mdadm --monitor" (or "-F") running? If you kill it does the disk > activity go away? > > NeilBrown yes I have (and have been) running "mdadm --monitor --scan —daemonise" I have /proc/sys/vm/block_dump enabled and it shows process mdadm acessing drives every 15 minutes. I wouldn’t be aware of mdadm being invoked elsewhere, so I presume it won’t happen when daemon is not running. Will see if I can get some more info with blktrace and report back.. -- 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
