Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 185456 - kernel dm mirroring: suspend operation is not well behaved
kernel dm mirroring: suspend operation is not well behaved
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Earl Brassow
Depends On:
Blocks: 181409
  Show dependency treegraph
Reported: 2006-03-14 16:53 EST by Jonathan Earl Brassow
Modified: 2007-11-30 17:07 EST (History)
7 users (show)

See Also:
Fixed In Version: RHSA-2006-0575
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-10 18:43:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
proposed (but not final) patch (1.33 KB, patch)
2006-03-14 16:55 EST, Jonathan Earl Brassow
no flags Details | Diff
better patch (3.07 KB, patch)
2006-04-01 15:00 EST, Jonathan Earl Brassow
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0575 normal SHIPPED_LIVE Important: Updated kernel packages available for Red Hat Enterprise Linux 4 Update 4 2006-08-10 00:00:00 EDT

  None (edit)
Description Jonathan Earl Brassow 2006-03-14 16:53:20 EST
Description of problem:

All outstanding I/O that the mirror has generated (recovery traffic) needs to be
completed before a return from mirror_postsuspend().  These are the rules of
device-mapper suspension, and mirroring is not following it.  This has cause
problems for other targets, and it is thought that it will cause problems for
mirroring during device failure scenarios.
Comment 1 Jonathan Earl Brassow 2006-03-14 16:55:20 EST
Created attachment 126122 [details]
proposed (but not final) patch
Comment 3 Jonathan Earl Brassow 2006-04-01 15:00:08 EST
Created attachment 127183 [details]
better patch

We must call log_postsuspend only _after_ all recovery work has been handled
and all associated calls to the log have been made.  Otherwise, the log can not
properly suspend, because it may be given work after the log postsuspend call. 
The fix involves a counter.
Comment 4 Jason Baron 2006-05-09 13:27:24 EDT
committed in stream U4 build 34.26. A test kernel with this patch is available
from http://people.redhat.com/~jbaron/rhel4/
Comment 8 Red Hat Bugzilla 2006-08-10 18:43:43 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.