From: Tim Small <tim@seoss.co.uk>
To: st0ff@npl.de
Cc: "Stefan /*St0fF*/ Hübner" <stefan.huebner@stud.tu-ilmenau.de>,
"Ian Dall" <ian@beware.dropbear.id.au>,
"Linux RAID" <linux-raid@vger.kernel.org>
Subject: Re: Device kicked from raid too easilly
Date: Tue, 08 Jun 2010 07:59:54 +0100 [thread overview]
Message-ID: <4C0DEA6A.8070107@seoss.co.uk> (raw)
In-Reply-To: <4C0DDB77.1070907@stud.tu-ilmenau.de>
On 08/06/10 06:56, Stefan /*St0fF*/ Hübner wrote:
> But I wouldn't want to subject it to the cabling, because (well, I'm not
> 100% sure if that's right) slot #1's cable is the shortest.
>
There are some scenarios where a shorter cable could show up a design
fault, when a longer cable wouldn't. I'm not an expert by any means,
and just off the top of my head, perhaps:
Over-saturated inputs
Stronger signal reflections
Auto-termination problems
I've certainly heard of badly designed Ethernet devices not working with
very short cable lengths....
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
--
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
prev parent reply other threads:[~2010-06-08 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 1:51 Device kicked from raid too easilly Ian Dall
2010-06-05 7:22 ` Stefan /*St0fF*/ Hübner
2010-06-08 5:15 ` Ian Dall
2010-06-08 5:56 ` Stefan /*St0fF*/ Hübner
2010-06-08 6:59 ` Tim Small [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=4C0DEA6A.8070107@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=ian@beware.dropbear.id.au \
--cc=linux-raid@vger.kernel.org \
--cc=st0ff@npl.de \
--cc=stefan.huebner@stud.tu-ilmenau.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).