From: Andy Smith <andy@strugglers.net>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Config option for removing bbl on assembly?
Date: Sat, 28 Nov 2020 20:59:53 +0000 [thread overview]
Message-ID: <20201128205953.GJ16071@bitfolk.com> (raw)
In-Reply-To: <1375483028.8430464.1606594500693.JavaMail.zimbra@karlsbakk.net>
Hi Roy,
On Sat, Nov 28, 2020 at 09:15:00PM +0100, Roy Sigurd Karlsbakk wrote:
> Will anyone look into this issue, please? It really is a problem.
Since it seems you can remove the BBL by removing and re-adding a
device I no longer see a need for a new option that removes it on
assembly.
Ideally I remember to do the remove and re-add before the machine is
put into service, but failing that just doing a remove and re-add
one time seems reasonable enough.
Cheers,
Andy
prev parent reply other threads:[~2020-11-28 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 7:45 Config option for removing bbl on assembly? Andy Smith
2020-09-12 10:58 ` Roy Sigurd Karlsbakk
2020-09-12 11:07 ` Andy Smith
2020-11-28 20:15 ` Roy Sigurd Karlsbakk
2020-11-28 20:59 ` Andy Smith [this message]
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=20201128205953.GJ16071@bitfolk.com \
--to=andy@strugglers.net \
--cc=linux-raid@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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;
as well as URLs for NNTP newsgroup(s).