From: Jens Axboe <axboe@kernel.dk>
To: Philipp Reisner <philipp.reisner@linbit.com>
Cc: linux-kernel@vger.kernel.org, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [GIT PULL] drbd-8.3 updates
Date: Fri, 18 May 2012 16:22:26 +0200 [thread overview]
Message-ID: <20120518142226.GF6496@kernel.dk> (raw)
In-Reply-To: <4277851.LeAnKnANCB@fat-tyre>
On Thu, May 10 2012, Philipp Reisner wrote:
> Hi Jens,
>
> This are the updates we have in the drbd-8.3 tree. They are intended
> for your "for-3.5/drivers" drivers branch.
>
> These changes include one new feature:
> * Allow detach from frozen backing devices with the new --force option;
> configurable timeout for backing devices by the new disk-timeout option
>
> And huge number of bug fixes:
> * Fixed a write ordering problem on SyncTarget nodes for a write
> to a block that gets resynced at the same time. The bug can
> only be triggered with a device that has a firmware that
> actually reorders writes to the same block
> * Fixed a race between disconnect and receive_state, that could cause
> a IO lockup
> * Fixed resend/resubmit for requests with disk or network timeout
> * Make sure that hard state changed do not disturb the connection
> establishing process (I.e. detach due to an IO error). When the
> bug was triggered it caused a retry in the connect process
> * Postpone soft state changes to no disturb the connection
> establishing process (I.e. becoming primary). When the bug
> was triggered it could cause both nodes going into SyncSource state
> * Fixed a refcount leak that could cause failures when trying to
> unload a protocol family modules, that was used by DRBD
> * Dedicated page pool for meta data IOs
> * Deny normal detach (as opposed to --forced) if the user tries
> to detach from the last UpToDate disk in the resource
> * Fixed a possible protocol error that could be caused by
> "unusual" BIOs.
> * Enforce the disk-timeout option also on meta-data IO operations
> * Implemented stable bitmap pages when we do a full write out of
> the bitmap
> * Fixed a rare compatibility issue with DRBD's older than 8.3.7
> when negotiating the bio_size
> * Fixed a rare race condition where an empty resync could stall with
> if pause/unpause events happen in parallel
> * Made the re-establishing of connections quicker, if it got a broken pipe
> once. Previously there was a bug in the code caused it to waste the first
> successful established connection after a broken pipe event.
>
> PS: I am postponing the drbd-8.4 for mainline for one or two kernel
> development cycles more (the ~400 patchets set).
>
> Best regards,
> Philipp
>
> The following changes since commit 0b7877d4eea3f93e3dd941999522bbd8c538cb53:
>
> Merge tag 'v3.4-rc5' into for-3.5/core (2012-05-01 14:29:55 +0200)
>
> are available in the git repository at:
>
> git@git.drbd.org:linux-drbd for-jens
Thanks, pulled in. Your git url confused me a bit, though, I pulled in
git://git.drbd.org/linux-drbd for-jens
Diffstat matches etc, so I'm jotting the above down to a typo in your
pull request script.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Philipp Reisner <philipp.reisner@linbit.com>
Cc: linux-kernel@vger.kernel.org, drbd-dev@lists.linbit.com
Subject: Re: [GIT PULL] drbd-8.3 updates
Date: Fri, 18 May 2012 16:22:26 +0200 [thread overview]
Message-ID: <20120518142226.GF6496@kernel.dk> (raw)
In-Reply-To: <4277851.LeAnKnANCB@fat-tyre>
On Thu, May 10 2012, Philipp Reisner wrote:
> Hi Jens,
>
> This are the updates we have in the drbd-8.3 tree. They are intended
> for your "for-3.5/drivers" drivers branch.
>
> These changes include one new feature:
> * Allow detach from frozen backing devices with the new --force option;
> configurable timeout for backing devices by the new disk-timeout option
>
> And huge number of bug fixes:
> * Fixed a write ordering problem on SyncTarget nodes for a write
> to a block that gets resynced at the same time. The bug can
> only be triggered with a device that has a firmware that
> actually reorders writes to the same block
> * Fixed a race between disconnect and receive_state, that could cause
> a IO lockup
> * Fixed resend/resubmit for requests with disk or network timeout
> * Make sure that hard state changed do not disturb the connection
> establishing process (I.e. detach due to an IO error). When the
> bug was triggered it caused a retry in the connect process
> * Postpone soft state changes to no disturb the connection
> establishing process (I.e. becoming primary). When the bug
> was triggered it could cause both nodes going into SyncSource state
> * Fixed a refcount leak that could cause failures when trying to
> unload a protocol family modules, that was used by DRBD
> * Dedicated page pool for meta data IOs
> * Deny normal detach (as opposed to --forced) if the user tries
> to detach from the last UpToDate disk in the resource
> * Fixed a possible protocol error that could be caused by
> "unusual" BIOs.
> * Enforce the disk-timeout option also on meta-data IO operations
> * Implemented stable bitmap pages when we do a full write out of
> the bitmap
> * Fixed a rare compatibility issue with DRBD's older than 8.3.7
> when negotiating the bio_size
> * Fixed a rare race condition where an empty resync could stall with
> if pause/unpause events happen in parallel
> * Made the re-establishing of connections quicker, if it got a broken pipe
> once. Previously there was a bug in the code caused it to waste the first
> successful established connection after a broken pipe event.
>
> PS: I am postponing the drbd-8.4 for mainline for one or two kernel
> development cycles more (the ~400 patchets set).
>
> Best regards,
> Philipp
>
> The following changes since commit 0b7877d4eea3f93e3dd941999522bbd8c538cb53:
>
> Merge tag 'v3.4-rc5' into for-3.5/core (2012-05-01 14:29:55 +0200)
>
> are available in the git repository at:
>
> git@git.drbd.org:linux-drbd for-jens
Thanks, pulled in. Your git url confused me a bit, though, I pulled in
git://git.drbd.org/linux-drbd for-jens
Diffstat matches etc, so I'm jotting the above down to a typo in your
pull request script.
--
Jens Axboe
next prev parent reply other threads:[~2012-05-18 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 12:19 [Drbd-dev] [GIT PULL] drbd-8.3 updates Philipp Reisner
2012-05-10 12:19 ` Philipp Reisner
2012-05-16 6:45 ` [Drbd-dev] " Robert Kim App and Facebook Marketing
2012-05-18 14:22 ` Jens Axboe [this message]
2012-05-18 14:22 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2012-10-02 13:02 [Drbd-dev] " Philipp Reisner
2012-10-03 6:44 ` Jens Axboe
2012-10-03 9:24 ` Philipp Reisner
2012-10-03 10:07 ` Philipp Reisner
2012-10-03 12:49 ` Jens Axboe
2012-10-03 13:49 ` Philipp Reisner
2012-10-03 14:04 ` Jens Axboe
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=20120518142226.GF6496@kernel.dk \
--to=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@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.