All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: mdraid <linux-raid@vger.kernel.org>
Subject: mdstat reporting (superblock & status side-by-side). Can it be changed ?
Date: Sun, 13 Sep 2015 12:58:25 -0500	[thread overview]
Message-ID: <55F5B941.8050107@suddenlinkmail.com> (raw)

All,

   After looking at the output of /proc/mdstat many times, there is one 'human 
factors' (human nature) bit of difficulty with the order of the output 
(especially with a standard 2-disk raid1 array and 1.2 superblock:

md1 : active raid1 sda7[2] sdb7[1]
       52396032 blocks super 1.2 [2/2] [UU]
                             ^^^^^^^^^

   When scanning the information quickly to insure you do NOT have 1/2 disks 
active in the array, you run into the version and disk information side-by-side.

   "1.2 [2/2]"

   Which naturally causes a short "huh?..., OK" double-take.

   Is there any way from a user standpoint (short of "read a b c d e f"; echo 
"$c $d $a $b $e $f"), to rearrange the order the information is reported as:

md1 : active raid1 sda7[2] sdb7[1]
       super 1.2 52396032 blocks [2/2] [UU]

   That simple change makes glancing down the right-side of the information much 
easier on the brain....

   I don't think this was ever a concern prior to the 1.2 superbock and I'm not 
sure it warrants any brainpower now. However, it was something that stood out to 
me, so I thought I would pass it along.

-- 
David C. Rankin, J.D.,P.E.

             reply	other threads:[~2015-09-13 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13 17:58 David C. Rankin [this message]
2015-09-13 18:09 ` mdstat reporting (superblock & status side-by-side). Can it be changed ? Roman Mamedov

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=55F5B941.8050107@suddenlinkmail.com \
    --to=drankinatty@suddenlinkmail.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 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.