From: "Jorge Fábregas" <jorge.fabregas@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Events Counter - How it increments
Date: Wed, 18 Nov 2020 22:21:31 -0400 [thread overview]
Message-ID: <f2d69b9a-9e2d-a104-0600-612f5d39084c@gmail.com> (raw)
In-Reply-To: <567bc78b-cf37-c40b-2e99-b86a80bdfb3e@suse.com>
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.
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?
Thanks.
--
Jorge
next prev parent reply other threads:[~2020-11-19 2:21 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 [this message]
2020-11-19 11:27 ` heming.zhao
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=f2d69b9a-9e2d-a104-0600-612f5d39084c@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).