Red Hat Bugzilla – Bug 504028
Improve Documentation of Cluster Mirror Configuration in LVM Manual
Last modified: 2009-09-03 11:55:27 EDT
Description of problem:
As of RHEL 5.3, cluster mirrors are supported in LVM. The documentation, however, should include more advice about general setup and configuration, and an example. With the help of Eduardo Damato, I have added this information to the RHEL 4.8 version of the document. I need to add comparable info for RHEL 5.4 (pushing it back to RHEL 5.3 if possible), updating for RHEL 5. There may also be a kbase article about how mirrors are reflected in the device mapper hierarchy, and I should check into referencing that when it is complete.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The info I added to 4.8 is in the draft of the 5.4 version and will be released with RHEL 5.4.
I've made all the changes indicated here -- with the exception of the following:
- Re: changing the examples so that they don't use the lock_nolock protocol --
that's actually a big task, both here and elsewhere, since when I originally
wrote this book all my examples were local. So to change that protocol I would
have to redo all of my examples either to be sure I was making everything
clustered, or to use a different file system than gfs/gfs2. For example, the vgs output in the examples would have to be changed to show the C attribute -- and I would want to run all the examples as clustered examples beginning to end, redoing all the setup and output. As I say, that's a large project.
And it gets even bigger: The entire GFS and GFS2 manuals are written with the assumption that you can use the file systems either in a cluster or locally (although why you'd use GFS locally is a question people have asked me here).
So what I'm going to do is open a separate bug for all my documentation, to say: update LVM and GFS and GFS2 documentation to account for deprecation of use of GFS/GFS2 file systems as local file systems.
- Also: I have not yet documented the first RHEL 5 release that supports the seg_pe_ranges option, as I'm waiting to find out which RHEL 5 release that was. As soon as I get that info I'll rebuild this document on the staging area and check it in and change the status of this bug to MODIFIED.
With the release of RHEL 5.4 I'm closing this bug.