Hello, mdadm --grow /dev/md2 --bitmap=internal mdadm: failed to set internal bitmap. I then tried it on md1 and this crashed my machine. (bitmap_endwrite <- handle_stripe) hmm. I don't know what to do. -- John 2012/3/3 Bryan Mesich <bryan.mesich@xxxxxxxx>: > On Sat, Mar 03, 2012 at 10:28:20PM +0100, John Obaterspok wrote: >> Please see below for errors I get when trying to add internal bitmap. > > [snip...] > >> okay, I'm trying to add an interal bitmap to see how much it slows down things: >> >> [root@Emperor ~]# mdadm --version >> mdadm - v3.2.3 - 23rd December 2011 >> >> >> [root@Emperor ~]# mdadm --grow --bitmap=internal /dev/md2 >> mdadm: failed to set internal bitmap. > > I think you are using the wrong cmd line syntax. Try the > following for adding an internal bitmap to /dev/md2 > > mdadm --grow /dev/md2 --bitmap=internal > > If you want to use an external bitmap, use --bitmap="path to > file". > >> [root@Emperor ~]# mdadm --examine-bitmap /dev/md2 >> Filename : /dev/md2 >> Magic : 00000000 >> mdadm: invalid bitmap magic 0x0, the bitmap file appears to be corrupted >> Version : 0 >> mdadm: unknown bitmap version 0, either the bitmap file is corrupted >> or you need to upgrade your tools >> > > [snip...] > > Bryan -- 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