All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roy Keene <rkeene@psislidell.com>
To: bernd-schubert@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with 2.6 kernel and lots of I/O
Date: Tue, 31 May 2005 14:00:46 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.62.0505311350330.7546@hammer.psislidell.com> (raw)
In-Reply-To: <200505312040.30812.bernd-schubert@web.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed, Size: 1221 bytes --]

Bernd,

 	The ENBD project requires a kernel patch for 2.6 support and I 
would like to remain with the vendor supplied (and "blessed" kernel) for 
support reasons.

 	Since I cannot provide feedback on the latest version of the 
kernel and I don't want to have an "unblessed" kernel, I've opened a 
ticket with RedHat attached to my support contract for this problem.  I 
mainly posted my question here to see if this was a known issue with 2.6 
in general or NBD-specific.

 	I had not heard of "DRBD" before now, but it looks interesting.  I 
am looking into it further.

Thanks,
 	Roy Keene

On Tue, 31 May 2005, Bernd Schubert wrote:

> Hello Roy,
>
> Roy Keene wrote:
>
>> Hello,
>>
>>   I have a (well, at least one) show-stopping problems with the 2.6
>> kernel while doing heavy I/O.  I have a (software) RAID1 of network block
>> devices (nbd0 and nbd1) set up on two identical machines in an
>
> what about using drbd or enbd? AFAIK both are much better tested/suited for
> network raid.
>
> Cheers,
>  Bernd
>
>
> -- 
> Bernd Schubert
> PCI / Theoretische Chemie
> Universität Heidelberg
> INF 229
> 69120 Heidelberg
> e-mail: bernd.schubert@pci.uni-heidelberg.de
>

  parent reply	other threads:[~2005-05-31 19:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 15:55 Problem with 2.6 kernel and lots of I/O Roy Keene
     [not found] ` <200505312040.30812.bernd-schubert@web.de>
2005-05-31 19:00   ` Roy Keene [this message]
2005-06-01  1:16     ` Kyle Moffett
2005-06-01 19:59 ` Pavel Machek
2005-06-05 10:11   ` Erik Slagter
2005-06-06  5:46     ` Kyle Moffett
2005-06-20 22:19       ` Roy Keene
2005-06-20 23:18         ` Kyle Moffett
2005-06-20 23:54           ` Roy Keene
2005-06-21  2:47             ` Kyle Moffett
2005-06-21  7:41             ` Pavel Machek
2005-06-21 14:23               ` Roy Keene
2005-05-31 16:12 Parag Warudkar

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=Pine.LNX.4.62.0505311350330.7546@hammer.psislidell.com \
    --to=rkeene@psislidell.com \
    --cc=bernd-schubert@gmx.de \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.