mirror of
git://sourceware.org/git/lvm2.git
synced 2025-03-11 20:58:50 +03:00
d34d2068dd
Previously, we were treating non-RAID to RAID up-converts as a "resync" operation. (The most common example being 'linear -> RAID1'.) RAID to RAID up-converts or rebuilds of specific RAID images are properly treated as a "recover" operation. Since we were treating some up-convert operations as "resync", it was possible to have scenarios where data corruption or data loss were possibilities if the RAID hadn't been able to sync completely before a loss of the primary source devices. In order to ensure that the user took the proper precautions in such scenarios, we required a '--force' option to be present. Unfortuneately, the force option was rendered useless because there was no way to distiguish the failure state of a potentially destructive repair from a nominal one - making the '--force' option a requirement for any RAID1 repair! We now treat non-RAID to RAID up-converts properly as "recover" operations. This eliminates the scenarios that can potentially cause data loss or data corruption; and this eliminates the need for the '--force' requirement. This patch removes the requirement to specify '--force' for RAID repairs.