From: "Jonathan Schmidt" <jon@impact-ltd.ca>
To: linux-raid@vger.kernel.org
Subject: Re: raidreconf error (bug)
Date: Sun, 18 Sep 2005 10:47:52 -0700 [thread overview]
Message-ID: <dgk989$f4n$1@sea.gmane.org> (raw)
In-Reply-To: 432D315E.10502@dtbb.net
Agreed, this would be an important fix to have committed back to the main
source. Unfortunately the fix I made was more of a band-aid hack and will
only work on drives that are exactly the same size as mine are -- not really
that useful in its current state. I've got my hands full backing up 300+GB
of data to DVDs and setting up a second server for replication, so I don't
have the time yet to generalize the fix. Perhaps in the next few weeks I
will have time to do so.
> Jonathan, did you also have the patch available for raidreconf? Please
> attach it to your reply to the raid list, I think it would be a good thing
> to have in the archive.
>
> Tyler.
prev parent reply other threads:[~2005-09-18 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 20:08 raidreconf error (bug) Jonathan Schmidt
2005-09-17 2:56 ` Jonathan Schmidt
2005-09-18 9:12 ` Tyler
2005-09-18 17:43 ` Jonathan Schmidt
2005-09-18 9:20 ` Tyler
2005-09-18 17:47 ` Jonathan Schmidt [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='dgk989$f4n$1@sea.gmane.org' \
--to=jon@impact-ltd.ca \
--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).