Linux RAID subsystem development
 help / color / mirror / Atom feed
From: 002@tut.by
To: Wols Lists <antlists@youngman.org.uk>
Cc: Linux-RAID <linux-raid@vger.kernel.org>,
	Andreas Klauer <andreas.klauer@metamorpher.de>,
	smartmontools-support@listi.jpberlin.de
Subject: Re: mdadm stuck at 0% reshape after grow
Date: Fri, 08 Dec 2017 04:25:06 +0300	[thread overview]
Message-ID: <438341512696306@web3g.yandex.ru> (raw)
In-Reply-To: <5A29D169.4000203@youngman.org.uk>


> If true, this actually has quite a big impact on hobbyist raid
> installations. 
Not really. SMART Command Transport is a feature, introduced long time ago. The last Seagate desktop drive model, not implementing it, is Barracuda 7200.10 (that's from year 2006), while WD and Hitachi had it even earlier. Besides, smartmontools version 5 behave as you expect it should (just checked that). So, the hypothetical problematic drive must be very old, but reused in fresh system, and also must be affected by long timeouts. Not very probable mix, IMHO.


  reply	other threads:[~2017-12-08  1:25 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
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 [this message]
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=438341512696306@web3g.yandex.ru \
    --to=002@tut.by \
    --cc=andreas.klauer@metamorpher.de \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=smartmontools-support@listi.jpberlin.de \
    /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