All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Config option for removing bbl on assembly?
Date: Sat, 12 Sep 2020 11:07:54 +0000	[thread overview]
Message-ID: <20200912110754.GE31926@bitfolk.com> (raw)
In-Reply-To: <583511729.466.1599908325671.JavaMail.zimbra@karlsbakk.net>

Hi Roy,

On Sat, Sep 12, 2020 at 12:58:45PM +0200, Roy Sigurd Karlsbakk wrote:
> …or just remove the whole bbl, since it has virtually no function
> and didn't even have it when it was introduced 10 years ago.

Yes, I saw your recent thread on the subject, and the others going
back years, and it did motivate me to think more about this.

I haven't seen an opinion from the current maintainers but I read that
Neil Brown thought it should not be removed but instead the bugs
should be found and fixed. So there doesn't seem to be any prospect
of this feature being removed.

Given that, and that there is a config option to disable it, I was
hoping it would be deemed less controversial to also have a way to
remove on next (incremental) assembly.

If you can't have your first choice of having the feature removed,
would you support that?

As an aside, I'm having a devil of a game trying to get the Debian
installer to let me use "CREATE bbl=no". Not only does
debian-installer use a config file at /tmp/mdadm.conf, but it
appears to constantly rewrite it every time you enter the MD
configuration section, so realistically it seems that the only way
to create arrays without a bbl is to do it manually from the d-i
shell.

    https://lists.debian.org/debian-boot/2020/09/msg00074.html

Cheers,
Andy

  reply	other threads:[~2020-09-12 11:08 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 [this message]
2020-11-28 20:15 ` Roy Sigurd Karlsbakk
2020-11-28 20:59   ` Andy Smith

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=20200912110754.GE31926@bitfolk.com \
    --to=andy@strugglers.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.