Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Edward Kuns <eddie.kuns@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: mdadm stuck at 0% reshape after grow
Date: Thu, 7 Dec 2017 10:26:16 +0000	[thread overview]
Message-ID: <5A291748.8020604@youngman.org.uk> (raw)
In-Reply-To: <CACsGCyTZaqRxWFJ1NxN3jVktRcQv3_AdjRTT+3OfuYMuFYdr_w@mail.gmail.com>

On 06/12/17 20:19, Edward Kuns wrote:
> 2) Wol, should there be a section on the Wiki about "Things you should
> make sure you have configured" that includes disabling the BBL (unless
> you know what you're doing), making sure you're scrubbing regularly,
> making sure you have drives that support scterc (or if you don't,
> configuring /sys/block/<device>/device/timeout), and so on?  Perhaps a
> list of information you should have handy before disaster strikes to
> make life a lot easier if it does?  E.g., running lsdrv or dumping
> partition tables to text files or listing information about your RAID
> configuration and LVM, etc.

A lot of that information is there. I'm just very conscious of the need
to make everything read well - too much documentation feels like it's
been thrown together, and is a horrible read.

One piece of documentation is a perfect example of how readers can miss
stuff because it's too obvious ... :-) I had trouble finding out how to
do some operation to do with text entry in a word processor. I couldn't
find any reference to it in the index. I searched high and low. Then
somebody pointed it out to me in the manual - it was repeated on nearly
every other page!

I'm planning to condense a lot of this thread into the "scary things
that are easy to fix" page, but your idea of a checklist page sounds
very good. Expect it to appear some time "soon" :-)

(Note also that a lot of this stuff I don't have personal experience of,
so it only tends to make its way into the wiki when something crops up
on the mailing list.)

Cheers,
Wol

  reply	other threads:[~2017-12-07 10:26 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 [this message]
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
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=5A291748.8020604@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=eddie.kuns@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox