From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Edward Kuns <eddie.kuns@gmail.com>
Cc: Phil Turmel <philip@turmel.org>,
Wols Lists <antlists@youngman.org.uk>,
Jeremy Graham <jeremy@doghouse.agency>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: mdadm stuck at 0% reshape after grow
Date: Thu, 7 Dec 2017 14:58:32 +0100 [thread overview]
Message-ID: <20171207135832.GA4858@metamorpher.de> (raw)
In-Reply-To: <CACsGCyTZaqRxWFJ1NxN3jVktRcQv3_AdjRTT+3OfuYMuFYdr_w@mail.gmail.com>
On Wed, Dec 06, 2017 at 02:19:17PM -0600, Edward Kuns wrote:
> 1) If I have bad blocks lists configured, how do I safely remove them?
--assemble with --update=no-bbl is safe, since it only removes if empty.
If not empty, likely you'll end up doing --update=force-no-bbl anyway.
> # smartctl -l scterc,70,70 /dev/sdb ; echo $?
> smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.8.13-100.fc23.x86_64]
> (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
>
> SCT Commands not supported
>
> 0
It'd be hilarious if the timeout FUD on this list came with advice that
didn't even do anything for most people, and nobody ever noticed...
Unfortunately, it returns 4 here. And there are years old posts that
explicitely check for it returning 4, so this shouldn't be new at all.
Perhaps it's an intermittent error specific to your smartctl version?
You can just set the timeouts unconditionally, if you really want them.
Regards
Andreas Klauer
next prev parent reply other threads:[~2017-12-07 13:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 9:41 mdadm stuck at 0% reshape after grow Jeremy Graham
2017-12-05 10:56 ` Wols Lists
2017-12-05 15:49 ` Nix
2017-12-05 15:55 ` 002
2017-12-06 2:51 ` Phil Turmel
2017-12-06 4:33 ` Jeremy Graham
2017-12-06 7:36 ` Jeremy Graham
2017-12-06 13:34 ` Wols Lists
2017-12-06 14:02 ` 002
2017-12-06 10:49 ` Andreas Klauer
2017-12-06 14:15 ` Phil Turmel
2017-12-06 16:03 ` Andreas Klauer
2017-12-06 16:21 ` Phil Turmel
2017-12-06 18:24 ` 002
2017-12-07 8:40 ` Jeremy Graham
2017-12-06 20:19 ` Edward Kuns
2017-12-07 10:26 ` Wols Lists
2017-12-07 13:58 ` Andreas Klauer [this message]
2017-12-07 17:06 ` Wols Lists
2017-12-07 17:40 ` Andreas Klauer
2017-12-07 20:31 ` Wols Lists
2017-12-07 23:40 ` Wols Lists
2017-12-08 1:25 ` 002
2017-12-09 0:20 ` Edward Kuns
2017-12-14 12:43 ` Brad Campbell
2017-12-14 17:32 ` Edward Kuns
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=20171207135832.GA4858@metamorpher.de \
--to=andreas.klauer@metamorpher.de \
--cc=antlists@youngman.org.uk \
--cc=eddie.kuns@gmail.com \
--cc=jeremy@doghouse.agency \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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