From: Philipp Reisner <philipp.reisner@linbit.com>
To: annoucements@drbd.org
Subject: [DRBD-announce] drbd-0.7.4.tar.gz
Date: Thu, 9 Sep 2004 23:13:44 +0200 [thread overview]
Message-ID: <200409092313.44641.philipp.reisner@linbit.com> (raw)
Hi,
I had the chance to install DRBD-0.7.3 on a SLES 8 system, and in
the progress I discovered a quite bad problem with Linux-2.4.x
and HIGHMEM. (This problem with HIGHMEM on Linux-2.4.x causes
DRBD to drop connection and reconnect quite often, which in
turn uncovered an other problem with caused the resync
progress to starve). -- BTW, all this happenden because a
paying custromer asked us to install drbd-0.7.x on the
Linux-2.4.x based system.
The other important fix is the support of devices bigger than
2TB.
So, you want to upgrade to this release, if you have huge
devices, or if you want to run on Linux-2.4.x with HIGHMEM.
Otherwise, this release offers nothing new for you.
0.7.4 (api:76/proto:74)
-----
* Fixed a critical bug with Linux-2.4.x and HIGHMEM!
* Fixed a bug that only showed up with the HIGHMEM problem on
Linux-2.4.x -> It caused the resync process to starve.
* The drbd.spec file now creates /dev/drbd in the post-install stage.
* Fixed support for more than 2TB storage. Now DRBD supports up to
3.99TB storage. It will also tell you, that it is not supported if
you try to set up a bigger device.
* Debian's build rules file now knows about the adjust_drbd_config_h.sh
file.
* DRBD_DISABLE_SENDPAGE available in drbd_config.h
-Philipp
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :
reply other threads:[~2004-09-09 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200409092313.44641.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=annoucements@drbd.org \
--cc=drbd-user@lists.linbit.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 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.