All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: "David C. Rankin" <drankinatty@suddenlinkmail.com>
Cc: mdraid <linux-raid@vger.kernel.org>
Subject: Re: mdstat reporting (superblock & status side-by-side). Can it be changed ?
Date: Sun, 13 Sep 2015 23:09:27 +0500	[thread overview]
Message-ID: <20150913230927.15cfa36a@natsu> (raw)
In-Reply-To: <55F5B941.8050107@suddenlinkmail.com>

[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]

On Sun, 13 Sep 2015 12:58:25 -0500
"David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:

>    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.

For me it does not. 1.2 is clearly different from 1/2, and the actual 2/2
that you have is even enclosed in brackets to stand out more prominently.

>    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....

If you want to simplify the mental processing, just look for any "_"s in the
string of "U"s which is also conveniently placed at the end of the line. In a
partially down RAID1 you'd have [U_] or [_U] there, which is very noticeable
compared to the usual [UU].

>    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.

I don't think it's justified to randomly change things around which many shell
scripts and the like are quite likely to depend on, just out of a personal
preference.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

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

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=20150913230927.15cfa36a@natsu \
    --to=rm@romanrm.net \
    --cc=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.