On Thu, 02 May 2013 10:34:58 +0200 Arkadiusz Bubała <arkadiusz.bubala@xxxxxxxxxx> wrote: > On 30.04.2013 03:48, NeilBrown wrote: > > On Mon, 29 Apr 2013 10:52:57 +0200 Arkadiusz Bubała > > <arkadiusz.bubala@xxxxxxxxxx> wrote: > > > > > >> Hello, > >> We've got a problem that sometimes mdadm monitor doesn't send events. > >> Actions are as follows: > >> > >> start: > >> create new RAID 5 array > >> wait until it's rebuilding > >> stop created array > >> go to start > >> > >> Only first time we get "NewArray" event then when new array is created > >> only "RebuildStarted" event appears. After our analysis we found out > >> that when we stop an array we get "DeviceDisapeared" event and when we > >> create a new array we get "RebuildFinished" and then "RebuildStarted" > >> event. Sometimes those two events don't show up. > >> > > The missing NewArray messages was fixed in June last year by > > commit 0f760384ebc92d81a988c1501e4a493ef064ad66 > > > > You are using a very old mdadm. Maybe you should try 3.2.6 > > > > I'm less sure about the RebuildStarted/RebuildFinished oddities but there is > > a good chance they are fixed is the latest release too. > > > > NeilBrown > > > > > Thank you, > I'm testing this on 3.2.6 and it seems to work well. Events don't > dissapear. We thought that lack of "NewArray" event may be intended. > > Could you answer these questions, please: > > Do we need to restart mdadm monitor when new disk is added to the system > (hotplug)? No. > > Do we need to generate config file in such situation or running mdadm > with option --scan is sufficient? > --scan should be sufficient. NeilBrown
Attachment:
signature.asc
Description: PGP signature
