linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jorge Fábregas" <jorge.fabregas@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Events Counter - How it increments
Date: Thu, 19 Nov 2020 07:46:35 -0400	[thread overview]
Message-ID: <847d5414-481f-5a5b-3a3d-e38861f3471f@gmail.com> (raw)
In-Reply-To: <4bade6e8-988c-11dd-0a77-5adffd926d7b@suse.com>

On 11/19/20 7:27 AM, heming.zhao@suse.com wrote:
> the status/event is the content of struct mdp_superblock_1:
>     __le64  ctime;      /* lo 40 bits are seconds, top 24 are microseconds or 0*/
>     __le32  level;      /* -4 (multipath), -1 (linear), 0,1,4,5 */
>     __le32  layout;     /* only for raid5 and raid10 currently */
>     __le64  size;       /* used size of component devices, in 512byte sectors */
> 
>     __le32  chunksize;  /* in 512byte sectors */
>     __le32  raid_disks;
>     ... ...
>     __le64  reshape_position;   /* next address in array-space for reshape */
>     __le32  delta_disks;    /* change in number of raid_disks       */
>     __le32  new_layout; /* new layout                   */
>     ... ...
>     __le32  dev_number; /* permanent identifier of this  device - not role in raid */
>     ... ...
>     __le16  dev_roles[0];   /* role in array, or 0xffff for a spare, or 0xfffe for faulty */ 
> 
> I am not very familiar with md, and can't enumerate all the cases. For your writing:
> failed disk - dev_roles[X]
> read errors - may change: dev_roles[X], recovery_offset
> array checks - normally won't change, except disk fail is detected
> commands by user - depend on special cmd

Thanks Heming for  the breakdown.  That was helpful.

-- -
Jorge


      reply	other threads:[~2020-11-19 11:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 14:24 Events Counter - How it increments Jorge Fábregas
2020-11-17 15:50 ` Jorge Fábregas
2020-11-18 16:45 ` heming.zhao
2020-11-19  2:21   ` Jorge Fábregas
2020-11-19 11:27     ` heming.zhao
2020-11-19 11:46       ` Jorge Fábregas [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=847d5414-481f-5a5b-3a3d-e38861f3471f@gmail.com \
    --to=jorge.fabregas@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;
as well as URLs for NNTP newsgroup(s).