AIX:Mirror Write Consistency: Difference between revisions

From RoggeWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
LVM ensures data consistency among mirrored copies. For every write to a volume, LVM generates a write request for every mirror copy. A problem might arise if the system crashes before all copies are written.
[[Category:AIX]]
[[Category:Logical Volume Manager]]


When mirror write consistency is active, LVM keeps additional information for recovery purposes. Mirror write consistency shoud be performed for most logical volumes. An exception is paging space, which does not use the existing date when the volumegroup is varied online.
The LVM always ensures data consistency among mirrored copies of a logical volume during normal I/O processing.


Tme MWC record consists of one sector and describes which logical partitions may be inconsistent if the system is not shutdown correctly. When the volumegroup is varied back online, this record is read to make the logical partitions consistent again.  
For every write to a logical volume, the LVM generates a write request for every mirror copy. A problem arises if the system crashes in the middle of processing a mirrored write (before all copies are written). If mirror write consistency recovery is requested for a logical volume, the LVM keeps additional information to allow recovery of these inconsistent mirrors. Mirror write consistency recovery should be performed for most mirrored logical volumes. Logical volumes, such as the page space that do not use the existing data when the volume group is re-varied on, do not need this protection.
The Mirror Write Consistency (MWC) record consists of one sector. It identifies which logical partitions may be inconsistent if the system is not shut down correctly. When the volume group is varied back on-line, this information is used to make the logical partitions consistent again.
Note: With Mirror Write Consistency LVs, because the MWC control sector is on the edge of the disk, performance may be improved if the mirrored logical volume is also on the edge.


Since AIX5, a mirror write consistency option called Passive Mirror Write Consistency is available. Default is Active MWC. Active MWC offers fast recovery at reboot after a crash has occurred. This benefit comes at the expense of write performance degradation, particularly in the case of random writes. Disabling Active MWC elimiates this penalty, but upon reboot the syncvg -f command must be issued to manually synchronize the volume group before users can access the volumegroup. To achieve this, automatic vary-on of volumegroups must be disabled.
Beginning in AIX® 5, a mirror write consistency option called Passive Mirror Write Consistency is available. The default mechanism for ensuring mirror write consistency is Active MWC. Active MWC provides fast recovery at reboot time after a crash has occurred. However, this benefit comes at the expense of write performance degradation, particularly in the case of random writes. Disabling Active MWC eliminates this write-performance penalty, but upon reboot after a crash you must use the syncvg -f command to manually synchronize the entire volume group before users can access the volume group. To achieve this, automatic vary-on of volume groups must be disabled.


Eneabling Passive MWC not only eliminates the write-performance penalty associated with Active MWC, but logical volumes will be automatically resynced as the partitions are being accessed. This means that the administrator does not have to synchronize logica volumes maunally or disable automatic vary-on. Disadvantage of Passive MWC is that slower read operations may occur until all partitions have been resynced.
Enabling Passive MWC not only eliminates the write-performance penalty associated with Active MWC, but logical volumes will be automatically resynchronized as the partitions are being accessed. This means that the administrator does not have to synchronize logical volumes manually or disable automatic vary-on. The disadvantage of Passive MWC is that slower read operations may occur until all the partitions have been resynchronized.
 
You can select either mirror write consistency option within SMIT when creating or changing a logical volume. The selection option takes effect only when the logical volume is mirrored (copies > 1).

Latest revision as of 14:17, 22 November 2010


The LVM always ensures data consistency among mirrored copies of a logical volume during normal I/O processing.

For every write to a logical volume, the LVM generates a write request for every mirror copy. A problem arises if the system crashes in the middle of processing a mirrored write (before all copies are written). If mirror write consistency recovery is requested for a logical volume, the LVM keeps additional information to allow recovery of these inconsistent mirrors. Mirror write consistency recovery should be performed for most mirrored logical volumes. Logical volumes, such as the page space that do not use the existing data when the volume group is re-varied on, do not need this protection. The Mirror Write Consistency (MWC) record consists of one sector. It identifies which logical partitions may be inconsistent if the system is not shut down correctly. When the volume group is varied back on-line, this information is used to make the logical partitions consistent again. Note: With Mirror Write Consistency LVs, because the MWC control sector is on the edge of the disk, performance may be improved if the mirrored logical volume is also on the edge.

Beginning in AIX® 5, a mirror write consistency option called Passive Mirror Write Consistency is available. The default mechanism for ensuring mirror write consistency is Active MWC. Active MWC provides fast recovery at reboot time after a crash has occurred. However, this benefit comes at the expense of write performance degradation, particularly in the case of random writes. Disabling Active MWC eliminates this write-performance penalty, but upon reboot after a crash you must use the syncvg -f command to manually synchronize the entire volume group before users can access the volume group. To achieve this, automatic vary-on of volume groups must be disabled.

Enabling Passive MWC not only eliminates the write-performance penalty associated with Active MWC, but logical volumes will be automatically resynchronized as the partitions are being accessed. This means that the administrator does not have to synchronize logical volumes manually or disable automatic vary-on. The disadvantage of Passive MWC is that slower read operations may occur until all the partitions have been resynchronized.

You can select either mirror write consistency option within SMIT when creating or changing a logical volume. The selection option takes effect only when the logical volume is mirrored (copies > 1).