From: David Greaves <david@dgreaves.com>
To: Dexter Filmore <Dexter.Filmore@gmx.de>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: when is a disk "non-fresh"?
Date: Sun, 10 Feb 2008 10:36:46 +0000 [thread overview]
Message-ID: <47AED3BE.50606@dgreaves.com> (raw)
In-Reply-To: <200802081032.26044.Dexter.Filmore@gmx.de>
Dexter Filmore wrote:
> On Friday 08 February 2008 00:22:36 Neil Brown wrote:
>> On Thursday February 7, Dexter.Filmore@gmx.de wrote:
>>> On Tuesday 05 February 2008 03:02:00 Neil Brown wrote:
>>>> On Monday February 4, Dexter.Filmore@gmx.de wrote:
>>>>> Seems the other topic wasn't quite clear...
>>>> not necessarily. sometimes it helps to repeat your question. there
>>>> is a lot of noise on the internet and somethings important things get
>>>> missed... :-)
>>>>
>>>>> Occasionally a disk is kicked for being "non-fresh" - what does this
>>>>> mean and what causes it?
>>>> The 'event' count is too small.
>>>> Every event that happens on an array causes the event count to be
>>>> incremented.
>>> An 'event' here is any atomic action? Like "write byte there" or "calc
>>> XOR"?
>> An 'event' is
>> - switch from clean to dirty
>> - switch from dirty to clean
>> - a device fails
>> - a spare finishes recovery
>> things like that.
>
> Is there a glossary that explains "dirty" and such in detail?
Not yet.
http://linux-raid.osdl.org/index.php?title=Glossary
David
prev parent reply other threads:[~2008-02-10 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 2:54 non-fresh: what? Dexter Filmore
2008-02-04 22:05 ` when is a disk "non-fresh"? Dexter Filmore
2008-02-05 2:02 ` Neil Brown
2008-02-07 22:16 ` Dexter Filmore
2008-02-07 23:22 ` Neil Brown
2008-02-08 9:32 ` Dexter Filmore
2008-02-10 10:36 ` David Greaves [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=47AED3BE.50606@dgreaves.com \
--to=david@dgreaves.com \
--cc=Dexter.Filmore@gmx.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).