On Tue, November 3, 2009 1:57 am, Jesse Wheeler wrote: > All: > > Thanks for the invaluable resource that is this mailing list. I've > learned quite a bit over the space of this month. > > I have the following configuration and question: > ..... > > Nov 2 09:15:42 fatboy dnsmasq[3648]: exiting on receipt of SIGTERM > Nov 2 09:15:43 fatboy dnsmasq[6922]: started, version 2.45 cachesize 150 > Nov 2 09:15:43 fatboy dnsmasq[6922]: compile time options: IPv6 > GNU-getopt no-ISC-leasefile no-DBus no-I18N TFTP > Nov 2 09:15:43 fatboy dnsmasq[6922]: using local addresses only for > domain devotioconsulting.net > Nov 2 09:15:43 fatboy dnsmasq[6922]: using nameserver 208.67.220.220#53 > Nov 2 09:15:43 fatboy dnsmasq[6922]: using nameserver 208.67.222.222#53 > Nov 2 09:15:43 fatboy dnsmasq[6922]: read /etc/hosts - 14 addresses > Nov 2 09:21:04 fatboy kernel: md: syncing RAID array md1 The only possible explanation for this that I can think of is the the array was started in 'auto-read-only' mode in which it will not write to the devices at all until a write request comes in through the top level device. Once that write request arrives, md accepts that the array really is meant to be used and starts any resync etc that might be needed. How is /dev/md1 used? Is it possible that nothing tried to write to it until this moment? If it was something started by a cron job, it would not say "resync =" but rather 'check =' or 'repair ='. NeilBrown -- 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
