From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: James Stephenson <inbox@jstephenson.me>, linux-raid@vger.kernel.org
Subject: Re: Unable to add journal device to RAID 6 array
Date: Fri, 6 May 2022 19:48:45 +0800 [thread overview]
Message-ID: <26c0f640-8801-240c-ce2c-99246b09f2e2@linux.dev> (raw)
In-Reply-To: <CA+an+MoM_Vb4Z3FSRcTo+ykmFTW5cwh1CQWCN9BMT45CdW_P0g@mail.gmail.com>
On 5/6/22 6:42 PM, James Stephenson wrote:
> Hi,
>
> First time using this (and indeed any) mailing list, so apologies if I
> violate any etiquette I'm not aware of!
>
> I'm trying to add a write-back journal device to an existing RAID 6
> array, and it's proving difficult. Essentially I did this:
>
> 1. Put the array in read-only
> 2. Attempt to add a journal device to the array
> 3. md said no because the array has a bitmap
> 4. I tried to remove the bitmap, and it said no: 'md: couldn't update
> array info. -16'
> 5. I rebooted
> 6. The array wouldn't start, and to my surprise was listed as having a
> journal device. Here's what it looked like:
> https://gist.github.com/jstephenson/1db2008c4243c2539d029f1f4706dc14
> 7. It was _very_ unhappy, and refused to do anything: 'md/raid:md126:
> array cannot have both journal and bitmap'
> 8. The only thing I could do was to zero the superblock on the journal
> device, and then fortunately everything assemble again nicely (with
> bitmap still in place)
>
> So, after a bit of messing around the array is back to where I
> started—RAID 6 with internal bitmap. However, I still cannot remove
> its bitmap.
>
> 1. sudo mdadm --grow /dev/md126 --bitmap=none
> 2. md: couldn't update array info. -16
-16 means EBUSY, so probably the array needs resync or recovery per
https://elixir.bootlin.com/linux/v5.10.106/source/drivers/md/md.c#L7374
Thanks,
Guoqing
next prev parent reply other threads:[~2022-05-06 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 10:42 Unable to add journal device to RAID 6 array James Stephenson
2022-05-06 11:48 ` Guoqing Jiang [this message]
2022-05-06 11:55 ` James Stephenson
2022-05-06 12:05 ` Guoqing Jiang
2022-05-06 13:25 ` James Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26c0f640-8801-240c-ce2c-99246b09f2e2@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=inbox@jstephenson.me \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox