Bug 453562

Summary: cmirror funktionality missing
Product: Red Hat Enterprise Linux 5 Reporter: Herbert L. Plankl <h.plankl>
Component: cmirrorAssignee: Jonathan Earl Brassow <jbrassow>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: low    
Version: 5.2CC: agk, ccaulfie, dwysocha, edamato, heinzm, mbroz
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-23 21:04:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Herbert L. Plankl 2008-07-01 10:08:50 UTC
Description of problem:
We are going to design and build a RedHat-HA-Cluster over 2 Datacenters for one
of our customers. We want to use GFS on top of a mirrored LVM-Volume (between 2
SANs) and so we really, really need the funktionality of cmirror.

When do you think is cmirror ready for use in a RHEL5-Cluster. I read something
about 5.2, but that seems to be wrong.

Version-Release number of selected component (if applicable):
Actually testing with RHEL5.2 cluster.

Additional info:
This cluster (a really huge one with about 8 HP-Blades, 2 eva-SANs and 1
ds8300-SAN, about 200TB Data, growing 2TB/month, 2 datacentres and so on..)
should go productive by the end of this year in one datacentre and then until
Dec 2009 complete productive in both datacentres.

Comment 1 Jonathan Earl Brassow 2008-07-01 15:22:00 UTC
Cluster mirror on rhel5 has been pushed out to 5.3.  There are builds available
for 5.2 if you would like to begin testing.  I would be happy to ask my manager
if he could include another beta tester in the 5.2 timeframe, if you like.


Comment 2 Herbert L. Plankl 2008-07-01 18:30:45 UTC
Yes, I would really like to test it.

Comment 3 Corey Marthaler 2008-07-23 21:04:42 UTC

*** This bug has been marked as a duplicate of 430797 ***