linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "heming.zhao@suse.com" <heming.zhao@suse.com>
To: "Jorge Fábregas" <jorge.fabregas@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Events Counter - How it increments
Date: Thu, 19 Nov 2020 19:27:03 +0800	[thread overview]
Message-ID: <4bade6e8-988c-11dd-0a77-5adffd926d7b@suse.com> (raw)
In-Reply-To: <f2d69b9a-9e2d-a104-0600-612f5d39084c@gmail.com>

Hello,

On 11/19/20 10:21 AM, Jorge Fábregas wrote:
> On 11/18/20 12:45 PM, heming.zhao@suse.com wrote:
>> The events is related with (struct mddev) mddev->events.
>> you can search it in kernel source code.
> 
> Thank you Heming.  I was expecting more of a general view since I'm a
> new user.  Sorry I wasn't clear.
>
very general overview: if array status/superblock is changed, event will increase.


> What sort of events cause the Event counter to increase?  If it's mainly
> whenever the superblock is updated then my question is: What sort of
> events cause the superblock to be updated? I can imagine detection of
> failed disk, read errors, array checks, commands by user/admin,
> assembly-reassembly etc? If an array operates fine for months - without
> user intervention,  will the Event counter increase at all?
> 

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
If an array operates fine for months - without user intervention - won't change

at last, please read the code.

Thanks.


  reply	other threads:[~2020-11-19 11:27 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 [this message]
2020-11-19 11:46       ` Jorge Fábregas

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=4bade6e8-988c-11dd-0a77-5adffd926d7b@suse.com \
    --to=heming.zhao@suse.com \
    --cc=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).