From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Wols Lists <antlists@youngman.org.uk>
Cc: "Roy Sigurd Karlsbakk" <roy@karlsbakk.net>,
"Linux RAID Mailing List" <linux-raid@vger.kernel.org>,
Håkon <hawken@thehawken.org>
Subject: Re: Feature request: Remove the badblocks list
Date: Tue, 18 Aug 2020 21:34:56 +0200 [thread overview]
Message-ID: <20200818193456.GA4066@lazy.lzy> (raw)
In-Reply-To: <5F3C2B4F.1050708@youngman.org.uk>
On Tue, Aug 18, 2020 at 08:26:07PM +0100, Wols Lists wrote:
> On 18/08/20 19:00, Roy Sigurd Karlsbakk wrote:
> > As far as I can understand, this list doesn't have any reason to exist, except to annoy sysadmins.
>
> Actually, there's at least one good reason for it to exist that I can
> think of - it *could* make recovering a broken array much easier. Think
> about it, I think it's documented in the wiki.
>
> That said, I'm hoping to do some work soon that will make it redundant.
>
> One little tip though - you've done a load of research to tell us what
> we already know - as documented on the wiki - and now you're asking us
> to do a load of work. If you want it done, well nobody else has bothered
> so far so what makes you think they'll bother now?
Is it really "a load of work" to switch for
default "on" to default "off"?
Because that's what he is asking.
If this is the case, there is something more
broken in the code...
BTW, I find it quite problematic too to have
a feature, activated by default, which is
_officially_ declared as *buggy*/
bye,
--
piergiorgio
next prev parent reply other threads:[~2020-08-18 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 18:00 Feature request: Remove the badblocks list Roy Sigurd Karlsbakk
2020-08-18 19:26 ` Wols Lists
2020-08-18 19:34 ` Piergiorgio Sartor [this message]
2020-08-18 19:43 ` Phil Turmel
2020-08-18 21:03 ` Håkon Struijk Holmen
2020-08-22 1:42 ` David C. Rankin
2020-09-02 13:36 ` Roy Sigurd Karlsbakk
2020-09-02 14:34 ` Adam Goryachev
2020-09-02 14:50 ` Roy Sigurd Karlsbakk
2020-09-02 15:09 ` Adam Goryachev
2020-09-02 15:25 ` Roy Sigurd Karlsbakk
2020-09-02 16:32 ` Adam Goryachev
2020-09-02 16:50 ` Roy Sigurd Karlsbakk
2020-09-02 19:45 ` Håkon Struijk Holmen
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=20200818193456.GA4066@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=antlists@youngman.org.uk \
--cc=hawken@thehawken.org \
--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 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.