From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Wilck Subject: Re: mdadm 3.3 fails to kick out non fresh disk Date: Tue, 24 Sep 2013 19:38:47 +0200 Message-ID: <5241CE27.30203@arcor.de> References: <20130914064305.0baadc69@notabene.brown> <20130914203800.385466b2@notabene.brown> <5234CA6A.3070305@arcor.de> <52373A19.7000105@arcor.de> <523C8EF9.60809@arcor.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Francis Moreau Cc: linux-raid List-Id: linux-raid.ids Hi Francis, > Could you show me the mdadm command I should use to insert sdb into the array ? I tried your scenario on HW with LSI fake RAID and encountered the same problem you had. I have come up with a patch that I've just posted ("Fix mdadm --add for LSI fake RAID" and follow-ups). Please try if this patch fixes your problem. To be precise, with this patch applied, mdadm /dev/md127 --add /dev/sdX should work again. You should be able to run this on your currently broken system if you somehow manage to transfer the updated mdadm and mdmon executables to that system, run mdmon --takeover /dev/md127, and then remove/add sdX again. The reason for the problem was a difference in the interpretation of the workspace_lba field in the DDF header between my code and LSI's. This has nothing to do with my previous patch "compare_super_ddf: fix sequence number check". Regards Martin