linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Phantazm" <phantazm@phantazm.nu>
To: linux-raid@vger.kernel.org
Subject: Re: Huge mdadm resync problem.
Date: Thu, 17 Feb 2005 13:37:43 +0100	[thread overview]
Message-ID: <cv231j$u49$1@sea.gmane.org> (raw)
In-Reply-To: cv219o$ose$1@sea.gmane.org

i forgot to mention that speed is generally no problem on the raid set.
It's connected to a gigabit interface and copying to and from the interface 
gives about 35mb/s over the link.
So disks are fast and IO is working pretty good.

Now i just sit here with my last hope on you fellas ;-)

Regards
Phantazm 




  reply	other threads:[~2005-02-17 12:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-17 12:08 Huge mdadm resync problem Phantazm
2005-02-17 12:37 ` Phantazm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-17 13:52 Lord Hess,Raum 301Kw,54-8994
2005-02-17 14:33 ` Phantazm
2005-02-17 14:40   ` Gordon Henderson
2005-02-17 14:57     ` Phantazm

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='cv231j$u49$1@sea.gmane.org' \
    --to=phantazm@phantazm.nu \
    --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).