From: David Greaves <david@dgreaves.com>
To: Neil Brown <neilb@cse.unsw.edu.au>, linux-raid@vger.kernel.org
Subject: Re: Force parity resync on raid5?
Date: Wed, 11 Aug 2004 10:23:25 +0100 [thread overview]
Message-ID: <4119E58D.8070404@dgreaves.com> (raw)
In-Reply-To: <16665.33845.170965.226004@cse.unsw.edu.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Neil Brown wrote:
|On Tuesday August 10, philip@corp.texas.net wrote:
|
|>Neil Brown wrote:
|>
|>>On Tuesday August 10, philip@corp.texas.net wrote:
|>>
|>>>Linux RAID *has* to have sort of way to force a parity resync. If it
|>>>doesn't have one, it needs one. That's a glaring omission to make.
|>>
|>>Well, you get what you pay for.....
|>
|>Tell me where to send the checks. Seriously. I know you guys work
hard
|>on this stuff and I will gladly donate to the fund to have important
(to
|>me) features implemented.
|
|Hmmm. Awkward.
|I'm not averse to doing a bit of contracting at times (taking un-paid
|leave or similar from my day job), but having a fund that people can
|donate to might be a bit more awkward...
So, given a request for a feature:
Set up a page with a rough estimate of the cost. eg, parity resync: 2
weeks effort @ £500/day (casually picked this as a v. cheap
'commercial consultant rate' - reasonable contract rate) is £5000.
Detailed estimate + design maybe a day or more at the same rate (maybe
just if anyone were to ask or mandatory if you felt you would need to
do this before committing to a feature).
You could add promise emails to the total (eg company X may promise
£2k but not until the rest has been promised up)
If you wanted to use a non-refundable paypal type account and update
the page as thankyous/donations/promises arrive, that could give
people an idea of the likely commitment elsewhere in the community -
and if you get a few £10 thankyous from home users then maybe it'll
affect your priority for stuff you'd have done at some point anyway.
And put the url in your .sig :)
Just a thought.
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBGeWN8LvjTle4P1gRApKmAJ4s+gngPl8W0FGqe2HduYQnkUuSPACePFJ2
p/a2zGQLm6xr8Ya/CRaKTOc=
=tWTX
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-08-11 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 12:03 Force parity resync on raid5? Philip Molter
2004-08-10 12:39 ` Neil Brown
2004-08-10 14:30 ` Philip Molter
2004-08-11 2:28 ` Neil Brown
2004-08-11 3:37 ` Philip Molter
2004-08-11 9:23 ` David Greaves [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 17:15 Salyzyn, Mark
2004-08-12 18:16 ` Guy
2004-08-09 23:10 Philip Molter
2004-08-10 9:04 ` Gordon Henderson
2004-08-12 4:06 ` Guy
2004-08-12 11:52 ` Philip Molter
2004-08-12 12:31 ` David Greaves
2004-08-12 15:22 ` Guy
2004-08-12 16:26 ` David Greaves
2004-08-12 17:07 ` Philip Molter
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=4119E58D.8070404@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).