Thanks for your reply. The bitmap state there was because the array was active at the time. I've found the issue however: it turns out that a previous 'check' must have been interrupted by power loss or similar, and so the array still had memory of this in some way (perhaps I could have seen this state in the sysfs tree somewhere?). After reading the comment in https://elixir.bootlin.com/linux/v5.10.106/source/drivers/md/md.h#L348 I thought I'd try a 'check' followed by an 'idle', and indeed after that I was able to successfully remove the bitmap and add a journal device :)! Thanks, James On Fri, 6 May 2022 at 13:05, Guoqing Jiang <guoqing.jiang@xxxxxxxxx> wrote: > > > > On 5/6/22 7:55 PM, James Stephenson wrote: > > Thank you for your reply. I did check the source and found the same > > block, however I’m not familiar enough to understand where I would see > > this condition indicated? > > > > As of now the array seems perfectly normal: > > https://gist.github.com/jstephenson/0b615aab33bb8157a3876471ef50424e > > Seems the bitmap is not clean, so resync thread might be running. > > bitmap: 3/88 pages [12KB], 65536KB chunk > > I suppose you can find relevant threads with "ps aux | grep md126", and also > the output of "cat /proc/mdstat" could be helpful. > > Thanks, > Guoqing
