From: Bill Davidsen <davidsen@tmr.com>
To: Tomka Gergely <tomka@avaxio.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid state diagram
Date: Mon, 28 May 2007 10:10:22 -0400 [thread overview]
Message-ID: <465AE2CE.1080901@tmr.com> (raw)
In-Reply-To: <46582FBC.3030305@avaxio.net>
Tomka Gergely wrote:
> Hi!
>
> I am drawing this picture for teaching:
>
> http://gergely.tomka.hu/kep/raidstates.png
>
> Is this a correct picture? I am not sure in the difference between
> active/clean and resync/recover.
>
> thanks for any comment.
Looks good to me, perhaps a copyright and creative commons license
statement would be useful to clarify what is fair use. That allows
others to use it for free projects, but you would still control
commercial use.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2007-05-28 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 13:01 raid state diagram Tomka Gergely
2007-05-28 14:10 ` Bill Davidsen [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=465AE2CE.1080901@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=tomka@avaxio.net \
/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).