diff options
| author | David Teigland <teigland@redhat.com> | 2019-01-30 09:55:34 -0600 |
|---|---|---|
| committer | David Teigland <teigland@redhat.com> | 2019-02-27 08:52:34 -0600 |
| commit | a9eaab6bebe1919b476ec3a4d094a4d6c512920e (patch) | |
| tree | 87beba6e7e30e1954ce7027e35d035a3de0c131b /tools/vgsplit.c | |
| parent | c8fc18e8bfbf6e81fc26c7cde780711db748f112 (diff) | |
| download | lvm2-a9eaab6bebe1919b476ec3a4d094a4d6c512920e.tar.gz | |
Use "cachevol" to refer to cache on a single LV
and "cachepool" to refer to a cache on a cache pool object.
The problem was that the --cachepool option was being used
to refer to both a cache pool object, and to a standard LV
used for caching. This could be somewhat confusing, and it
made it less clear when each kind would be used. By
separating them, it's clear when a cachepool or a cachevol
should be used.
Previously:
- lvm would use the cache pool approach when the user passed
a cache-pool LV to the --cachepool option.
- lvm would use the cache vol approach when the user passed
a standard LV in the --cachepool option.
Now:
- lvm will always use the cache pool approach when the user
uses the --cachepool option.
- lvm will always use the cache vol approach when the user
uses the --cachevol option.
Diffstat (limited to 'tools/vgsplit.c')
| -rw-r--r-- | tools/vgsplit.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/vgsplit.c b/tools/vgsplit.c index 87f48df8a..7150570a6 100644 --- a/tools/vgsplit.c +++ b/tools/vgsplit.c @@ -402,7 +402,7 @@ static int _move_cache(struct volume_group *vg_from, /* NOTREACHED */ - if (lv_is_cache(lv) && lv_is_cache_single(seg->pool_lv)) { + if (lv_is_cache(lv) && lv_is_cache_vol(seg->pool_lv)) { log_error("Cannot split while LV %s has cache attached.", display_lvname(lv)); return 0; } else if (lv_is_cache(lv)) { |