mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maurice Volaski <mvolaski@aecom.yu.edu>
To: Lee Revell <rlrevell@joe-job.com>
Cc: drbd-user@linbit.com, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.13 is hiding devices from /dev [Was Why is the  kernel hiding drbd devices?}
Date: Wed, 7 Sep 2005 00:45:16 -0400	[thread overview]
Message-ID: <a0623090dbf441d7a72a0@[129.98.90.227]> (raw)
In-Reply-To: <1126063875.13159.31.camel@mindpipe>

>What is drbd?  An out of tree driver?  Did it work with 2.6.13-rcX?  If

Yes, it implements RAID 1 across two computers over a network link in 
realtime. Generally, you combine with a program called heartbeat to 
implement high-availabilty failover. It's very neat ;-)

>not, why didn't they tell us sooner?  Does it expect devfs to be present
>in the kernel by any chance?


It's actually working now. Don't ask me to explain it because last 
night and most of Monday I couldn't get it working and I must have 
compiled half a dozen different Gentoo kernel versions of 2.6.12, and 
it worked with some but not others. It worked perfectly with the 
official 2.6.12 but not with official 2.6.13. Then suddenly it just 
started to work again on all the Gentoo 2.6.12s it wouldn't work with 
and also with the official 2.6.13. I have 2.6.13 running right now, 
and drbd devices show up in /dev as if there never had been any 
problem.
-- 

Maurice Volaski, mvolaski@aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University

  reply	other threads:[~2005-09-07  4:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 21:13 Maurice Volaski
2005-09-07  3:31 ` Lee Revell
2005-09-07  4:45   ` Maurice Volaski [this message]
2005-09-07  5:03     ` Lee Revell
2005-09-07  5:30       ` Kernel 2.6.13 is NOT " Lars Ellenberg

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='a0623090dbf441d7a72a0@[129.98.90.227]' \
    --to=mvolaski@aecom.yu.edu \
    --cc=drbd-user@linbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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

all inboxes | Powered by JetHome®