shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2025-01-18 10:04:20 +03:00
Code Releases Activity
lvm2/lib/activate/dev_manager.h

121 lines
4.7 KiB
C
Raw Normal View History

o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
/*
Update copyright notices.
2004-03-30 19:35:44 +00:00
* Copyright (C) 2002-2004 Sistina Software, Inc. All rights reserved.
Add activation/read_only_volume_list to override LV permission in metadata.
2012-01-12 01:51:56 +00:00
* Copyright (C) 2004-2012 Red Hat, Inc. All rights reserved.
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
*
Update copyright notices.
2004-03-30 19:35:44 +00:00
* This file is part of LVM2.
*
* This copyrighted material is made available to anyone wishing to use,
* modify, copy, or redistribute it subject to the terms and conditions
Fix inconsistent licence notices: executables are GPLv2; libraries LGPLv2.1.
2007-08-20 20:55:30 +00:00
* of the GNU Lesser General Public License v.2.1.
Update copyright notices.
2004-03-30 19:35:44 +00:00
*
Fix inconsistent licence notices: executables are GPLv2; libraries LGPLv2.1.
2007-08-20 20:55:30 +00:00
* You should have received a copy of the GNU Lesser General Public License
Update copyright notices.
2004-03-30 19:35:44 +00:00
* along with this program; if not, write to the Free Software Foundation,
doc: change fsf address Hmm rpmlint suggest fsf is using a different address these days, so lets keep it up-to-date
2016-01-21 11:49:46 +01:00
* Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
*/
#ifndef _LVM_DEV_MANAGER_H
#define _LVM_DEV_MANAGER_H
build: Don't generate symlinks in include/ dir As we start refactoring the code to break dependencies (see doc/refactoring.txt), I want us to use full paths in the includes (eg, #include "base/data-struct/list.h"). This makes it more obvious when we're breaking abstraction boundaries, eg, including a file in metadata/ from base/
2018-05-14 10:30:20 +01:00
#include "lib/metadata/metadata-exported.h"
Introduce percent_range_t and centralise snapshot full/mirror in-sync checks.
2009-10-01 00:35:29 +00:00
Begin to separate out segment types.
2004-05-04 21:25:57 +00:00
struct logical_volume;
Add lv_activate_opts structure To avoid modification of 'read-only' volume group structure add a new structure to pass local data around the code for LV activation. As origin_only is one such flag - replace this parameter with new struct lv_activate_opts. More parameters might eventually become part of lv_activate_opts.
2011-06-17 14:14:19 +00:00
struct lv_activate_opts;
Use dm_is_dm_major instead of local copy. Allow mapped devices to be used as PVs safely.
2005-10-25 19:08:21 +00:00
struct volume_group;
Begin to separate out segment types.
2004-05-04 21:25:57 +00:00
struct cmd_context;
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
struct dev_manager;
Tidy various pre-processing incl. making libdl optional.
2003-03-24 18:08:53 +00:00
struct dm_info;
Use dm_is_dm_major instead of local copy. Allow mapped devices to be used as PVs safely.
2005-10-25 19:08:21 +00:00
struct device;
dev_manager: enhance dev_manager_info to acquire LV segment status if requested, add lv_info_with_seg_status fn
2014-11-04 15:00:32 +01:00
struct lv_seg_status;
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
snapshot: keep COW writable for read-only volumes When snapshot is created in read-only mode with 'lvcreate -s -pr...', lvm2 still needs to be able to write to layered -cow volume to store metadata and exceptions blocks. TODO: in some case we might be able to do full tree with read-only volume but this probably needs futher validation: 1. checking snapshot header already exist 2. origin & snapshot are both in read-only mode.
2018-03-08 10:27:04 +01:00
int read_only_lv(const struct logical_volume *lv, const struct lv_activate_opts *laopts, const char *layer);
Add activation/read_only_volume_list to override LV permission in metadata.
2012-01-12 01:51:56 +00:00
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
/*
* Constructor and destructor.
*/
Begin to separate out segment types.
2004-05-04 21:25:57 +00:00
struct dev_manager *dev_manager_create(struct cmd_context *cmd,
Major pvmove fix to issue ioctls in the correct order when multiple LVs are affected by the move. (Currently it's possible for I/O to become trapped between suspended devices amongst other problems. The current fix was selected so as to minimise the testing surface. I hope eventually to replace it with a cleaner one that extends the deptree code. Some lvconvert scenarios still suffer from related problems.
2011-06-11 00:03:06 +00:00
const char *vg_name,
unsigned track_pvmove_deps);
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
void dev_manager_destroy(struct dev_manager *dm);
Fix lvcreate corelog validation. Add --config for overriding most config file settings from cmdline. Quote arguments when printing command line. Remove linefeed from 'initialising logging' message. Add 'Completed' debug message. Don't attempt library exit after reloading config files. Always compile with libdevmapper, even if device-mapper is disabled.
2006-05-16 16:48:31 +00:00
void dev_manager_release(void);
Another sync point - numerous fixes & clean ups.
2003-07-04 22:34:56 +00:00
void dev_manager_exit(void);
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
/*
* The device handler is responsible for creating all the layered
* dm devices, and ensuring that all constraints are maintained
* (eg, an origin is created before its snapshot, but is not
* unsuspended until the snapshot is also created.)
*/
activation: Skip another non-prefixed info ioctl. _percent() also does a lookup by dm uuid. Also get kernel version from cmd->kernel_vsn.
2016-04-08 16:27:12 +01:00
int dev_manager_info(struct cmd_context *cmd, const struct logical_volume *lv,
Allow internal suspend and resume of origin without its snapshots.
2010-08-17 16:25:32 +00:00
const char *layer,
Always query device by uuid only. lvm2 devices have always UUID set even if imported from lvm1 metadata. Patch removes name argument from dev_manager_info call and converts all activation related calls to use query by UUID. Also it simplifies mknode call (which is the only user on mknodes parameter).
2010-02-24 20:00:56 +00:00
int with_open_count, int with_read_ahead,
dev_manager: enhance dev_manager_info to acquire LV segment status if requested, add lv_info_with_seg_status fn
2014-11-04 15:00:32 +01:00
struct dm_info *dminfo, uint32_t *read_ahead,
struct lv_seg_status *seg_status);
activation: Skip another non-prefixed info ioctl. _percent() also does a lookup by dm uuid. Also get kernel version from cmd->kernel_vsn.
2016-04-08 16:27:12 +01:00
Rename; add some FIXMEs.
2002-05-22 14:03:45 +00:00
int dev_manager_snapshot_percent(struct dev_manager *dm,
more snapshot code tidying
2006-04-06 14:06:27 +00:00
const struct logical_volume *lv,
report: select: refactor: move percent handling code to libdm for reuse
2014-06-09 12:08:27 +02:00
dm_percent_t *percent);
pvmove support
2003-04-30 15:26:25 +00:00
int dev_manager_mirror_percent(struct dev_manager *dm,
Change dev_manager_mirror_percent()'s 'struct logical_volume *' to be 'const'. Be consistent with its use (and dev_manager_snapshot_percent()). Pass 'lv' from dev_manager_snapshot_percent() to _percent() to _percent_run(). _percent_run() always dereferenced 'lv' (when initializing segh) even though it may have been NULL (as was the case until now for dev_manager_snapshot_percent()). If a "snapshot-origin" LV (snapshot-merge whose merge was deferred becuase it was open) was passed to _percent_run() it would always return 100%. Update _percent_run() to NOT return PERCENT_100 et. al. if ->target_percent() wasn't ever called and supplied 'lv' is a merging origin. A default return of 100% does not work for snapshot-merge. Also tweak a related lvconvert log_error() to include "Aborting merge."
2010-01-15 22:58:25 +00:00
const struct logical_volume *lv, int wait,
report: select: refactor: move percent handling code to libdm for reuse
2014-06-09 12:08:27 +02:00
dm_percent_t *percent, uint32_t *event_nr);
RAID: Add RAID status accessibility functions Similar to the way thin* accesses its kernel status, we add a method for RAID to grab the various values in its status output without the higher levels (LVM) having to understand how to parse the output. Added functions include: - lib/activate/dev_manager.c:dev_manager_raid_status() Pulls the status line from the kernel - libdm/libdm-deptree.c:dm_get_status_raid() Parses status line and puts components into dm_status_raid struct - lib/activate/activate.c:lv_raid_dev_health() Accesses dm_status_raid to deliver raid dev_health string The new structure and functions can provide a more unified way to access status information. ('lv_raid_percent' could switch to using these functions, for example.)
2013-02-01 11:31:47 -06:00
int dev_manager_raid_status(struct dev_manager *dm,
const struct logical_volume *lv,
struct dm_status_raid **status);
RAID: Add scrubbing support for RAID LVs New options to 'lvchange' allow users to scrub their RAID LVs. Synopsis: lvchange --syncaction {check|repair} vg/raid_lv RAID scrubbing is the process of reading all the data and parity blocks in an array and checking to see whether they are coherent. 'lvchange' can now initaite the two scrubbing operations: "check" and "repair". "check" will go over the array and recored the number of discrepancies but not repair them. "repair" will correct the discrepancies as it finds them. 'lvchange --syncaction repair vg/raid_lv' is not to be confused with 'lvconvert --repair vg/raid_lv'. The former initiates a background synchronization operation on the array, while the latter is designed to repair/replace failed devices in a mirror or RAID logical volume. Additional reporting has been added for 'lvs' to support the new operations. Two new printable fields (which are not printed by default) have been added: "syncaction" and "mismatches". These can be accessed using the '-o' option to 'lvs', like: lvs -o +syncaction,mismatches vg/lv "syncaction" will print the current synchronization operation that the RAID volume is performing. It can be one of the following: - idle: All sync operations complete (doing nothing) - resync: Initializing an array or recovering after a machine failure - recover: Replacing a device in the array - check: Looking for array inconsistencies - repair: Looking for and repairing inconsistencies The "mismatches" field with print the number of descrepancies found during a check or repair operation. The 'Cpy%Sync' field already available to 'lvs' will print the progress of any of the above syncactions, including check and repair. Finally, the lv_attr field has changed to accomadate the scrubbing operations as well. The role of the 'p'artial character in the lv_attr report field as expanded. "Partial" is really an indicator for the health of a logical volume and it makes sense to extend this include other health indicators as well, specifically: 'm'ismatches: Indicates that there are discrepancies in a RAID LV. This character is shown after a scrubbing operation has detected that portions of the RAID are not coherent. 'r'efresh : Indicates that a device in a RAID array has suffered a failure and the kernel regards it as failed - even though LVM can read the device label and considers the device to be ok. The LV should be 'r'efreshed to notify the kernel that the device is now available, or the device should be 'r'eplaced if it is suspected of failing.
2013-04-11 15:33:59 -05:00
int dev_manager_raid_message(struct dev_manager *dm,
const struct logical_volume *lv,
const char *msg);
Add dm-writecache support dm-writecache is used like dm-cache with a standard LV as the cache. $ lvcreate -n main -L 128M -an foo /dev/loop0 $ lvcreate -n fast -L 32M -an foo /dev/pmem0 $ lvconvert --type writecache --cachepool fast foo/main $ lvs -a foo -o+devices LV VG Attr LSize Origin Devices [fast] foo -wi------- 32.00m /dev/pmem0(0) main foo Cwi------- 128.00m [main_wcorig] main_wcorig(0) [main_wcorig] foo -wi------- 128.00m /dev/loop0(0) $ lvchange -ay foo/main $ dmsetup table foo-main_wcorig: 0 262144 linear 7:0 2048 foo-main: 0 262144 writecache p 253:4 253:3 4096 0 foo-fast: 0 65536 linear 259:0 2048 $ lvchange -an foo/main $ lvconvert --splitcache foo/main $ lvs -a foo -o+devices LV VG Attr LSize Devices fast foo -wi------- 32.00m /dev/pmem0(0) main foo -wi------- 128.00m /dev/loop0(0)
2018-08-27 14:53:09 -05:00
int dev_manager_writecache_message(struct dev_manager *dm,
const struct logical_volume *lv,
const char *msg);
cache: New functions for gathering info on cache devices Building on the new DM function that parses DM cache status, we introduce the following LVM level functions to aquire information about cache devices: - lv_cache_block_info: retrieves information on the cache's block/chunk usage - lv_cache_policy_info: retrieves information on the cache's policy
2014-01-28 12:24:51 -06:00
int dev_manager_cache_status(struct dev_manager *dm,
const struct logical_volume *lv,
cache: lv_cache_status Replace lv_cache_block_info() and lv_cache_policy_info() with lv_cache_status() which directly returns dm_status_cache structure together with some calculated values. After use mem pool stored inside lv_status_cache structure needs to be destroyed.
2014-11-03 12:52:29 +01:00
struct lv_status_cache **status);
Thin add lv_thin_pool_transaction_id Easy function to get transaction_id status value.
2012-01-25 08:48:42 +00:00
int dev_manager_thin_pool_status(struct dev_manager *dm,
const struct logical_volume *lv,
thin: use noflush for obtaining transaction_id Do not flush thin pool data, when reading transation_id status.
2013-01-17 10:54:41 +01:00
struct dm_status_thin_pool **status,
setup_task: add with_flush To get better control when flushing is used add extra arg when setting up dm task. By default now check dm device status without flush. (At this moment this should effect only thin and cache volumes). Also switch dev_manager_thin_pool_status() to use more readable 'flush' parameter instead of 'no_flush'.
2016-05-27 13:45:47 +02:00
int flush);
Thin add dev_manager_thin_pool_percent dev manager function to read percent info from thin pool.
2011-12-21 13:09:33 +00:00
int dev_manager_thin_pool_percent(struct dev_manager *dm,
const struct logical_volume *lv,
report: select: refactor: move percent handling code to libdm for reuse
2014-06-09 12:08:27 +02:00
int metadata, dm_percent_t *percent);
Thin add function to read thin volume percent This value returns percentage of 'mapped' size compared with total LV size. (Without passed seg pointer it return highest mapped size - but it's not used yet.)
2012-01-19 15:27:54 +00:00
int dev_manager_thin_percent(struct dev_manager *dm,
const struct logical_volume *lv,
report: select: refactor: move percent handling code to libdm for reuse
2014-06-09 12:08:27 +02:00
int mapped, dm_percent_t *percent);
thin: read table line with thin device id Add functions to parse thin table line to obtain thin device id.
2013-12-04 13:57:27 +01:00
int dev_manager_thin_device_id(struct dev_manager *dm,
const struct logical_volume *lv,
uint32_t *device_id);
dev_manager: add dev_manager_vdo_pool_status
2018-06-29 11:15:54 +02:00
int dev_manager_vdo_pool_status(struct dev_manager *dm,
const struct logical_volume *lv,
vdo: minor API cleanup Since the parse_vdo_pool_status() become vdo_manip API part, and there will be no 'dm' matching status parser, the API can be simplified and closely match thin API here.
2019-01-21 00:48:05 +01:00
struct lv_status_vdo **vdo_status,
int flush);
cleanup: constify activation usage of lv pointer Let's enforce cheking of write access to LV by compiler. Activation part does never need to write anything to LV so keep LV pointer const.
2014-09-22 15:50:07 +02:00
int dev_manager_suspend(struct dev_manager *dm, const struct logical_volume *lv,
Add lv_activate_opts structure To avoid modification of 'read-only' volume group structure add a new structure to pass local data around the code for LV activation. As origin_only is one such flag - replace this parameter with new struct lv_activate_opts. More parameters might eventually become part of lv_activate_opts.
2011-06-17 14:14:19 +00:00
struct lv_activate_opts *laopts, int lockfs, int flush_required);
cleanup: constify activation usage of lv pointer Let's enforce cheking of write access to LV by compiler. Activation part does never need to write anything to LV so keep LV pointer const.
2014-09-22 15:50:07 +02:00
int dev_manager_activate(struct dev_manager *dm, const struct logical_volume *lv,
Add lv_activate_opts structure To avoid modification of 'read-only' volume group structure add a new structure to pass local data around the code for LV activation. As origin_only is one such flag - replace this parameter with new struct lv_activate_opts. More parameters might eventually become part of lv_activate_opts.
2011-06-17 14:14:19 +00:00
struct lv_activate_opts *laopts);
cleanup: constify activation usage of lv pointer Let's enforce cheking of write access to LV by compiler. Activation part does never need to write anything to LV so keep LV pointer const.
2014-09-22 15:50:07 +02:00
int dev_manager_preload(struct dev_manager *dm, const struct logical_volume *lv,
Add lv_activate_opts structure To avoid modification of 'read-only' volume group structure add a new structure to pass local data around the code for LV activation. As origin_only is one such flag - replace this parameter with new struct lv_activate_opts. More parameters might eventually become part of lv_activate_opts.
2011-06-17 14:14:19 +00:00
struct lv_activate_opts *laopts, int *flush_required);
cleanup: constify activation usage of lv pointer Let's enforce cheking of write access to LV by compiler. Activation part does never need to write anything to LV so keep LV pointer const.
2014-09-22 15:50:07 +02:00
int dev_manager_deactivate(struct dev_manager *dm, const struct logical_volume *lv);
int dev_manager_transient(struct dev_manager *dm, const struct logical_volume *lv) __attribute__((nonnull(1, 2)));
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
Always query device by uuid only. lvm2 devices have always UUID set even if imported from lvm1 metadata. Patch removes name argument from dev_manager_info call and converts all activation related calls to use query by UUID. Also it simplifies mknode call (which is the only user on mknodes parameter).
2010-02-24 20:00:56 +00:00
int dev_manager_mknodes(const struct logical_volume *lv);
The LVM2 part of vgmknodes [still to do the non-devfs device-mapper bit].
2003-11-12 19:16:48 +00:00
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
/*
* Put the desired changes into effect.
*/
int dev_manager_execute(struct dev_manager *dm);
Add mirror_library description to example.conf. More compile-time cleanup.
2006-05-11 17:58:58 +00:00
int dev_manager_device_uses_vg(struct device *dev,
Use dm_is_dm_major instead of local copy. Allow mapped devices to be used as PVs safely.
2005-10-25 19:08:21 +00:00
struct volume_group *vg);
Allow dm-cache cache device to be standard LV If a single, standard LV is specified as the cache, use it directly instead of converting it into a cache-pool object with two separate LVs (for data and metadata). With a single LV as the cache, lvm will use blocks at the beginning for metadata, and the rest for data. Separate dm linear devices are set up to point at the metadata and data areas of the LV. These dm devs are given to the dm-cache target to use. The single LV cache cannot be resized without recreating it. If the --poolmetadata option is used to specify an LV for metadata, then a cache pool will be created (with separate LVs for data and metadata.) Usage: $ lvcreate -n main -L 128M vg /dev/loop0 $ lvcreate -n fast -L 64M vg /dev/loop1 $ lvs -a vg LV VG Attr LSize Type Devices main vg -wi-a----- 128.00m linear /dev/loop0(0) fast vg -wi-a----- 64.00m linear /dev/loop1(0) $ lvconvert --type cache --cachepool fast vg/main $ lvs -a vg LV VG Attr LSize Origin Pool Type Devices [fast] vg Cwi---C--- 64.00m linear /dev/loop1(0) main vg Cwi---C--- 128.00m [main_corig] [fast] cache main_corig(0) [main_corig] vg owi---C--- 128.00m linear /dev/loop0(0) $ lvchange -ay vg/main $ dmsetup ls vg-fast_cdata (253:4) vg-fast_cmeta (253:5) vg-main_corig (253:6) vg-main (253:24) vg-fast (253:3) $ dmsetup table vg-fast_cdata: 0 98304 linear 253:3 32768 vg-fast_cmeta: 0 32768 linear 253:3 0 vg-main_corig: 0 262144 linear 7:0 2048 vg-main: 0 262144 cache 253:5 253:4 253:6 128 2 metadata2 writethrough mq 0 vg-fast: 0 131072 linear 7:1 2048 $ lvchange -an vg/min $ lvconvert --splitcache vg/main $ lvs -a vg LV VG Attr LSize Type Devices fast vg -wi------- 64.00m linear /dev/loop1(0) main vg -wi------- 128.00m linear /dev/loop0(0)
2018-08-17 15:45:52 -05:00
int dev_manager_remove_dm_major_minor(uint32_t major, uint32_t minor);
dev_manager: add dev_manager_remove_dm_major_minor Move DM usage into dev_manager.c source file. Also convert STATUS to INFO ioctl - as that's enough to obtain UUID - this also avoid issuing unwanted flush on checked DM device for being mpath.
2019-03-13 12:59:59 +01:00
int dev_manager_check_prefix_dm_major_minor(uint32_t major, uint32_t minor, const char *prefix);
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.
2019-01-30 09:55:34 -06:00
int get_cache_vol_meta_data(struct cmd_context *cmd,
Allow dm-cache cache device to be standard LV If a single, standard LV is specified as the cache, use it directly instead of converting it into a cache-pool object with two separate LVs (for data and metadata). With a single LV as the cache, lvm will use blocks at the beginning for metadata, and the rest for data. Separate dm linear devices are set up to point at the metadata and data areas of the LV. These dm devs are given to the dm-cache target to use. The single LV cache cannot be resized without recreating it. If the --poolmetadata option is used to specify an LV for metadata, then a cache pool will be created (with separate LVs for data and metadata.) Usage: $ lvcreate -n main -L 128M vg /dev/loop0 $ lvcreate -n fast -L 64M vg /dev/loop1 $ lvs -a vg LV VG Attr LSize Type Devices main vg -wi-a----- 128.00m linear /dev/loop0(0) fast vg -wi-a----- 64.00m linear /dev/loop1(0) $ lvconvert --type cache --cachepool fast vg/main $ lvs -a vg LV VG Attr LSize Origin Pool Type Devices [fast] vg Cwi---C--- 64.00m linear /dev/loop1(0) main vg Cwi---C--- 128.00m [main_corig] [fast] cache main_corig(0) [main_corig] vg owi---C--- 128.00m linear /dev/loop0(0) $ lvchange -ay vg/main $ dmsetup ls vg-fast_cdata (253:4) vg-fast_cmeta (253:5) vg-main_corig (253:6) vg-main (253:24) vg-fast (253:3) $ dmsetup table vg-fast_cdata: 0 98304 linear 253:3 32768 vg-fast_cmeta: 0 32768 linear 253:3 0 vg-main_corig: 0 262144 linear 7:0 2048 vg-main: 0 262144 cache 253:5 253:4 253:6 128 2 metadata2 writethrough mq 0 vg-fast: 0 131072 linear 7:1 2048 $ lvchange -an vg/min $ lvconvert --splitcache vg/main $ lvs -a vg LV VG Attr LSize Type Devices fast vg -wi------- 64.00m linear /dev/loop1(0) main vg -wi------- 128.00m linear /dev/loop0(0)
2018-08-17 15:45:52 -05:00
struct logical_volume *lv,
struct logical_volume *pool_lv,
struct dm_info *info_meta, struct dm_info *info_data);
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.
2019-01-30 09:55:34 -06:00
int remove_cache_vol_meta_data(struct cmd_context *cmd,
Allow dm-cache cache device to be standard LV If a single, standard LV is specified as the cache, use it directly instead of converting it into a cache-pool object with two separate LVs (for data and metadata). With a single LV as the cache, lvm will use blocks at the beginning for metadata, and the rest for data. Separate dm linear devices are set up to point at the metadata and data areas of the LV. These dm devs are given to the dm-cache target to use. The single LV cache cannot be resized without recreating it. If the --poolmetadata option is used to specify an LV for metadata, then a cache pool will be created (with separate LVs for data and metadata.) Usage: $ lvcreate -n main -L 128M vg /dev/loop0 $ lvcreate -n fast -L 64M vg /dev/loop1 $ lvs -a vg LV VG Attr LSize Type Devices main vg -wi-a----- 128.00m linear /dev/loop0(0) fast vg -wi-a----- 64.00m linear /dev/loop1(0) $ lvconvert --type cache --cachepool fast vg/main $ lvs -a vg LV VG Attr LSize Origin Pool Type Devices [fast] vg Cwi---C--- 64.00m linear /dev/loop1(0) main vg Cwi---C--- 128.00m [main_corig] [fast] cache main_corig(0) [main_corig] vg owi---C--- 128.00m linear /dev/loop0(0) $ lvchange -ay vg/main $ dmsetup ls vg-fast_cdata (253:4) vg-fast_cmeta (253:5) vg-main_corig (253:6) vg-main (253:24) vg-fast (253:3) $ dmsetup table vg-fast_cdata: 0 98304 linear 253:3 32768 vg-fast_cmeta: 0 32768 linear 253:3 0 vg-main_corig: 0 262144 linear 7:0 2048 vg-main: 0 262144 cache 253:5 253:4 253:6 128 2 metadata2 writethrough mq 0 vg-fast: 0 131072 linear 7:1 2048 $ lvchange -an vg/min $ lvconvert --splitcache vg/main $ lvs -a vg LV VG Attr LSize Type Devices fast vg -wi------- 64.00m linear /dev/loop1(0) main vg -wi------- 128.00m linear /dev/loop0(0)
2018-08-17 15:45:52 -05:00
struct dm_info *info_meta, struct dm_info *info_data);
o Sync with cvs, dev_manager still needs to be wired into activate.c
2002-02-25 12:02:33 +00:00
#endif
Copy Permalink