linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Alberto Alonso <alberto@ggsys.net>
Cc: Doug Ledford <dledford@redhat.com>, linux-raid@vger.kernel.org
Subject: Re: Implementing low level timeouts within MD
Date: Fri, 02 Nov 2007 08:44:34 -0400	[thread overview]
Message-ID: <472B1BB2.2060302@tmr.com> (raw)
In-Reply-To: <1193992909.3649.75.camel@w100>

Alberto Alonso wrote:
> On Thu, 2007-11-01 at 15:16 -0400, Doug Ledford wrote:
>   
>> Not in the older kernel versions you were running, no.
>>     
>
> These "old versions" (specially the RHEL) are supposed to be
> the official versions supported by Redhat and the hardware 
> vendors, as they were very specific as to what versions of 
> Linux were supported.

So the vendors of the failing drives claimed that these kernels were 
supported? That's great, most vendors don't even consider Linux 
supported. What response did you get when you reported the problem to 
Redhat on your RHEL support contract? Did they agree that this hardware, 
and its use for software raid, was supported and intended?

>  Of all people, I would think you would
> appreciate that. Sorry if I sound frustrated and upset, but 
> it is clearly a result of what "supported and tested" really 
> means in this case. I don't want to go into a discussion of
> commercial distros, which are "supported" as this is nor the
> time nor the place but I don't want to open the door to the
> excuse of "its an old kernel", it wasn't when it got installed.
>   
The problem is in the time travel module. It didn't properly cope with 
future hardware, and since you have very long uptimes, I'm reasonably 
sure you haven't updated the kernel to get fixes installed.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  parent reply	other threads:[~2007-11-02 12:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 17:12 Implementing low level timeouts within MD Alberto Alonso
2007-10-26 19:00 ` Doug Ledford
2007-10-27 10:33   ` Samuel Tardieu
2007-10-30  5:19     ` Alberto Alonso
2007-10-30 17:39       ` Doug Ledford
2007-11-01  5:08         ` Alberto Alonso
2007-11-01 14:14           ` Bill Davidsen
2007-11-01 19:16           ` Doug Ledford
2007-11-02  8:41             ` Alberto Alonso
2007-11-02 11:09               ` David Greaves
2007-11-02 17:47                 ` Alberto Alonso
2007-11-02 12:44               ` Bill Davidsen [this message]
2007-11-02 15:45               ` Doug Ledford
2007-11-02 18:21                 ` Alberto Alonso
2007-11-02 19:15                   ` Doug Ledford
2007-11-02 21:24                     ` Alberto Alonso
2007-10-27 21:46   ` Alberto Alonso
2007-10-27 23:55     ` Doug Ledford
2007-10-28  6:27       ` Alberto Alonso
2007-10-29 17:22         ` Doug Ledford
2007-10-30  5:08           ` Alberto Alonso
2007-10-30 12:12             ` Gabor Gombas
2007-10-30 17:58             ` Doug Ledford
2007-11-01 14:19             ` Bill Davidsen
2007-11-07  8:47           ` Goswin von Brederlow
2007-10-27 18:59 ` Richard Scobie
     [not found]   ` <1193522726.7690.31.camel@w100>
2007-10-27 23:46     ` Richard Scobie
2007-10-30  4:47 ` Neil Brown

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=472B1BB2.2060302@tmr.com \
    --to=davidsen@tmr.com \
    --cc=alberto@ggsys.net \
    --cc=dledford@redhat.com \
    --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).