shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-22 17:35:59 +03:00
Code Releases Activity
1587236089
lvm2/lib/report/columns.h

191 lines
18 KiB
C
Raw Normal View History

New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
/*
Update columns.h comment to describe macro args.
2009-04-23 20:27:58 +04:00
* Copyright (C) 2002-2004 Sistina Software, Inc. All rights reserved.
lib/properties: Common code for handling properties. The common bits from lib/report/properties.[c|h] have been moved to lib/properties/prop_common.[c|h] to allow re-use of property handling functionality without polluting the report handling functionality. Signed-off-by: Tony Asleson <tasleson@redhat.com>
2013-07-12 21:09:44 +04:00
* Copyright (C) 2004-2013 Red Hat, Inc. All rights reserved.
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
*
Update copyright notices.
2004-03-30 23:35:44 +04: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-21 00:55:30 +04:00
* of the GNU Lesser General Public License v.2.1.
Update copyright notices.
2004-03-30 23:35:44 +04:00
*
Fix inconsistent licence notices: executables are GPLv2; libraries LGPLv2.1.
2007-08-21 00:55:30 +04:00
* You should have received a copy of the GNU Lesser General Public License
Update copyright notices.
2004-03-30 23:35:44 +04:00
* along with this program; if not, write to the Free Software Foundation,
* Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
*/
Update columns.h comment to describe macro args.
2009-04-23 20:27:58 +04:00
/*
* This file defines the fields (columns) for the reporting commands
* (pvs/vgs/lvs).
reporting: tidy recent new fields Add underscores and prefixes to recently-added fields. (Might add more alias functionality in future.)
2013-07-19 04:30:02 +04:00
*
* The preferred order of the field descriptions in the help text
* determines the order the entries appear in this file.
*
* When adding new entries take care to use the existing style.
* Displayed fields names normally have a type prefix and use underscores.
* Field-specific internal functions names normally match the displayed
* field names but without underscores.
* Help text ends with a full stop.
Update columns.h comment to describe macro args.
2009-04-23 20:27:58 +04:00
*/
Add 'flags' field to columns.h and define FIELD_MODIFIABLE. Add a 'flags' field to columns.h, and set it to 0 by default. Define FIELD_MODIFIABLE flag to indicate whether a 'set' function exists to change the field's value.
2010-08-20 16:44:03 +04:00
cleanup: use macros for definition of reporting/selection reserved values The macros for reserved value definition makes the process a bit easier, but there's still a place for improvement and make this even more transparent. We can optimize and provide better automatism here later on.
2014-07-08 14:40:45 +04:00
/*
* FIELD(report_object_type, structure, sort_type, heading, structure_field, output width, reporting_function, field_id, description, settable_via_lib)
*/
Allow for specification of major number as well as minor.
2003-04-02 23:14:43 +04:00
/* *INDENT-OFF* */
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(LVS, lv, STR, "LV UUID", lvid.id[1], 38, uuid, lv_uuid, "Unique identifier.", 0)
FIELD(LVS, lv, STR, "LV", lvid, 4, lvname, lv_name, "Name. LVs created for internal use are enclosed in brackets.", 0)
report: Add lv_dm_path and lv_full_name fields.
2014-07-02 20:24:05 +04:00
FIELD(LVS, lv, STR, "LV", lvid, 4, lvfullname, lv_full_name, "Full name of LV including its VG, namely VG/LV.", 0)
FIELD(LVS, lv, STR, "Path", lvid, 4, lvpath, lv_path, "Full pathname for LV. Blank for internal LVs.", 0)
FIELD(LVS, lv, STR, "DMPath", lvid, 6, lvdmpath, lv_dm_path, "Internal device-mapper pathname for LV (in /dev/mapper directory).", 0)
report: Add lv_parent field. Only defined for thin/cache/raid/mirror at this stage as it relies on get_only_segment_using_this_lv().
2014-07-04 02:49:34 +04:00
FIELD(LVS, lv, STR, "Parent", lvid, 6, lvparent, lv_parent, "For LVs that are components of another LV, the parent LV.", 0)
report: add separate LVSINFOSTATUS field type for info+status combined fields Add separate LVSINFOSTATUS field type for fields which display both dm info-like and dm status-like information. The internal interface is there with the introduction of LVSSTATUS field type which can cope with the combination of LVSSTATUS and LVSINFO field types (several fields). However, till now, we considered that *single* field can display either LVSINFO or LVSSTATUS, but not both at the same time. Till now, we haven't had single field which needs both - hence add LVSINFOSTATUS field type for such fields as we currently need this for the lv_attr field which requires combination of info and status. This patch just adds interface for an ability to register such fields (the code that copes with this is already in).
2015-01-20 18:02:48 +03:00
FIELD(LVSINFOSTATUS, lv, STR, "Attr", lvid, 4, lvstatus, lv_attr, "Various attributes - see man page.", 0)
Add lv_layout_and_type fn, lv_layout and lv_type reporting fields. The lv_layout and lv_type fields together help with LV identification. We can do basic identification using the lv_attr field which provides very condensed view. In contrast to that, the new lv_layout and lv_type fields provide more detialed information on exact layout and type used for LVs. For top-level LVs which are pure types not combined with any other LV types, the lv_layout value is equal to lv_type value. For non-top-level LVs which may be combined with other types, the lv_layout describes the underlying layout used, while the lv_type describes the use/type/usage of the LV. These two new fields are both string lists so selection (-S/--select) criteria can be defined using the list operators easily: [] for strict matching {} for subset matching. For example, let's consider this: $ lvs -a -o name,vg_name,lv_attr,layout,type LV VG Attr Layout Type [lvol1_pmspare] vg ewi------- linear metadata,pool,spare pool vg twi-a-tz-- pool,thin pool,thin [pool_tdata] vg rwi-aor--- level10,raid data,pool,thin [pool_tdata_rimage_0] vg iwi-aor--- linear image,raid [pool_tdata_rimage_1] vg iwi-aor--- linear image,raid [pool_tdata_rimage_2] vg iwi-aor--- linear image,raid [pool_tdata_rimage_3] vg iwi-aor--- linear image,raid [pool_tdata_rmeta_0] vg ewi-aor--- linear metadata,raid [pool_tdata_rmeta_1] vg ewi-aor--- linear metadata,raid [pool_tdata_rmeta_2] vg ewi-aor--- linear metadata,raid [pool_tdata_rmeta_3] vg ewi-aor--- linear metadata,raid [pool_tmeta] vg ewi-aor--- level1,raid metadata,pool,thin [pool_tmeta_rimage_0] vg iwi-aor--- linear image,raid [pool_tmeta_rimage_1] vg iwi-aor--- linear image,raid [pool_tmeta_rmeta_0] vg ewi-aor--- linear metadata,raid [pool_tmeta_rmeta_1] vg ewi-aor--- linear metadata,raid thin_snap1 vg Vwi---tz-k thin snapshot,thin thin_snap2 vg Vwi---tz-k thin snapshot,thin thin_vol1 vg Vwi-a-tz-- thin thin thin_vol2 vg Vwi-a-tz-- thin multiple,origin,thin Which is a situation with thin pool, thin volumes and thin snapshots. We can see internal 'pool_tdata' volume that makes up thin pool has actually a level10 raid layout and the internal 'pool_tmeta' has level1 raid layout. Also, we can see that 'thin_snap1' and 'thin_snap2' are both thin snapshots while 'thin_vol1' is thin origin (having multiple snapshots). Such reporting scheme provides much better base for selection criteria in addition to providing more detailed information, for example: $ lvs -a -o name,vg_name,lv_attr,layout,type -S 'type=metadata' LV VG Attr Layout Type [lvol1_pmspare] vg ewi------- linear metadata,pool,spare [pool_tdata_rmeta_0] vg ewi-aor--- linear metadata,raid [pool_tdata_rmeta_1] vg ewi-aor--- linear metadata,raid [pool_tdata_rmeta_2] vg ewi-aor--- linear metadata,raid [pool_tdata_rmeta_3] vg ewi-aor--- linear metadata,raid [pool_tmeta] vg ewi-aor--- level1,raid metadata,pool,thin [pool_tmeta_rmeta_0] vg ewi-aor--- linear metadata,raid [pool_tmeta_rmeta_1] vg ewi-aor--- linear metadata,raid (selected all LVs which are related to metadata of any type) lvs -a -o name,vg_name,lv_attr,layout,type -S 'type={metadata,thin}' LV VG Attr Layout Type [pool_tmeta] vg ewi-aor--- level1,raid metadata,pool,thin (selected all LVs which hold metadata related to thin) lvs -a -o name,vg_name,lv_attr,layout,type -S 'type={thin,snapshot}' LV VG Attr Layout Type thin_snap1 vg Vwi---tz-k thin snapshot,thin thin_snap2 vg Vwi---tz-k thin snapshot,thin (selected all LVs which are thin snapshots) lvs -a -o name,vg_name,lv_attr,layout,type -S 'layout=raid' LV VG Attr Layout Type [pool_tdata] vg rwi-aor--- level10,raid data,pool,thin [pool_tmeta] vg ewi-aor--- level1,raid metadata,pool,thin (selected all LVs with raid layout, any raid layout) lvs -a -o name,vg_name,lv_attr,layout,type -S 'layout={raid,level1}' LV VG Attr Layout Type [pool_tmeta] vg ewi-aor--- level1,raid metadata,pool,thin (selected all LVs with raid level1 layout exactly) And so on...
2014-08-13 12:03:45 +04:00
FIELD(LVS, lv, STR_LIST, "Layout", lvid, 10, lvlayout, lv_layout, "LV layout.", 0)
refactor: rename 'lv_type' field to 'lv_role' The 'lv_type' field name was a bit misleading. Better one is 'lv_role' since this fields describes what's the actual use of the LV currently - its 'role'.
2014-08-25 11:07:03 +04:00
FIELD(LVS, lv, STR_LIST, "Role", lvid, 10, lvrole, lv_role, "LV role.", 0)
report: 'whether' -> 'set if' in field description
2014-07-09 15:41:25 +04:00
FIELD(LVS, lv, BIN, "InitImgSync", lvid, 10, lvinitialimagesync, lv_initial_image_sync, "Set if mirror/RAID images underwent initial resynchronization.", 0)
FIELD(LVS, lv, BIN, "ImgSynced", lvid, 10, lvimagesynced, lv_image_synced, "Set if mirror/RAID image is synchronized.", 0)
FIELD(LVS, lv, BIN, "Merging", lvid, 10, lvmerging, lv_merging, "Set if snapshot LV is being merged to origin.", 0)
FIELD(LVS, lv, BIN, "Converting", lvid, 10, lvconverting, lv_converting, "Set if LV is being converted.", 0)
report: add separate fields for PV/VG/LV attributes Physical Volume Fields: pv_allocatable - Whether this device can be used for allocation. pv_exported - Whether this device is exported. pv_missing - Whether this device is missing in system. Volume Group Fields: vg_permissions - VG permissions. vg_extendable - Whether VG is extendable. vg_exported - Whether VG is exported. vg_partial - Whether VG is partial. vg_allocation_policy - VG allocation policy. vg_clustered - Whether VG is clustered. Logical Volume Fields: lv_volume_type - LV volume type. lv_initial_image_sync - Whether mirror/RAID images underwent initial resynchronization. lv_image_synced - Whether mirror/RAID image is synchronized. lv_merging - Whether snapshot LV is being merged to origin. lv_converting - Whether LV is being converted. lv_allocation_policy - LV allocation policy. lv_allocation_locked - Whether LV is locked against allocation changes. lv_fixed_minor - Whether LV has fixed minor number assigned. lv_merge_failed - Whether snapshot merge failed. lv_snapshot_invalid - Whether snapshot LV is invalid. lv_target_type - Kernel target type the LV is related to. lv_health_status - LV health status. lv_skip_activation - Whether LV is skipped on activation. Logical Volume Info Fields lv_permissions - LV permissions. lv_suspended - Whether LV is suspended. lv_live_table - Whether LV has live table present. lv_inactive_table - Whether LV has inactive table present. lv_device_open - Whether LV device is open.
2014-07-02 13:09:14 +04:00
FIELD(LVS, lv, STR, "AllocPol", lvid, 10, lvallocationpolicy, lv_allocation_policy, "LV allocation policy.", 0)
report: 'whether' -> 'set if' in field description
2014-07-09 15:41:25 +04:00
FIELD(LVS, lv, BIN, "AllocLock", lvid, 10, lvallocationlocked, lv_allocation_locked, "Set if LV is locked against allocation changes.", 0)
FIELD(LVS, lv, BIN, "FixMin", lvid, 10, lvfixedminor, lv_fixed_minor, "Set if LV has fixed minor number assigned.", 0)
FIELD(LVS, lv, BIN, "MergeFailed", lvid, 15, lvmergefailed, lv_merge_failed, "Set if snapshot merge failed.", 0)
FIELD(LVS, lv, BIN, "SnapInvalid", lvid, 15, lvsnapshotinvalid, lv_snapshot_invalid, "Set if snapshot LV is invalid.", 0)
FIELD(LVS, lv, BIN, "SkipAct", lvid, 15, lvskipactivation, lv_skip_activation, "Set if LV is skipped on activation.", 0)
report: rename lv_error_when_full field to lv_when_full and display either "error", "queue" or "" Rename original lv_error_when_full field to lv_when_full and also convert it from binary field to string field displaying three possible values: "error", "queueu" or "" (blank for undefined). $ lvs vg/pool vg/pool1 vg/linear_lv -o+lv_when_full LV VG Attr LSize Data% Meta% WhenFull linear_lv vg -wi-a----- 4.00m pool vg twi-aotz-- 4.00m 0.00 0.98 queue pool1 vg twi-a-tz-- 4.00m 0.00 0.88 error For -S|--select these synonyms are recognized: "error" -> "error when full", "error if no space" "queue" -> "queue when full", "queue if no space" "" -> "undefined"
2015-01-21 12:43:40 +03:00
FIELD(LVS, lv, STR, "WhenFull", lvid, 15, lvwhenfull, lv_when_full, "For thin pools, behavior when full.", 0)
reporting: tidy recent new fields Add underscores and prefixes to recently-added fields. (Might add more alias functionality in future.)
2013-07-19 04:30:02 +04:00
FIELD(LVS, lv, STR, "Active", lvid, 6, lvactive, lv_active, "Active state of the LV.", 0)
report: display 'unknown' value for active/active_locally/active_remotely/active_exclusively if info bypassed Before the patch: $ lvs -o name,active vg/lvol1 --driverloaded n WARNING: Activation disabled. No device-mapper interaction will beattempted. LV Active lvol1 active With this patch applied: $ lvs -o name,active vg/lvol1 --driverloaded n WARNING: Activation disabled. No device-mapper interaction will be attempted. LV Active lvol1 unknown The same for active_{locally,remotely,exclusively} fields. Also, rename headings for these fields (ActLocal/ActRemote/ActExcl).
2014-07-11 13:15:06 +04:00
FIELD(LVS, lv, BIN, "ActLocal", lvid, 10, lvactivelocally, lv_active_locally, "Set if the LV is active locally.", 0)
FIELD(LVS, lv, BIN, "ActRemote", lvid, 10, lvactiveremotely, lv_active_remotely, "Set if the LV is active remotely.", 0)
FIELD(LVS, lv, BIN, "ActExcl", lvid, 10, lvactiveexclusively, lv_active_exclusively, "Set if the LV is active exclusively.", 0)
lvm2app: Add signed numerical property values Currently lvm2app properties have the following structure: typedef struct lvm_property_value { uint32_t is_settable:1; uint32_t is_string:1; uint32_t is_integer:1; uint32_t is_valid:1; uint32_t padding:28; union { const char *string; uint64_t integer; } value; } lvm_property_value_t; which assumes that numerical values were in the range of 0 to 2**64-1. However, some of the properties were 'signed', like LV major/minor numbers and some reserved values for properties that represent percentages. Thus when the values were retrieved they were in two's complement notation. So for a -1 major number the API user would get a value of 18446744073709551615. The API user could cast the returned value to an int64_t to handle this, but that requires the API developer to look at the source code and determine when it should be done. This change modifies the return property structure to: typedef struct lvm_property_value { uint32_t is_settable:1; uint32_t is_string:1; uint32_t is_integer:1; uint32_t is_valid:1; uint32_t is_signed:1; uint32_t padding:27; union { const char *string; uint64_t integer; int64_t signed_integer; } value; } lvm_property_value_t; With this addition the API user can interrogate that the value is numerical, (is_integer = 1) and subsequently check if it's signed (is_signed = 1) too. If signed, then the API developer should use the union's signed_integer to avoid casting. This change maintains backwards compatibility as the structure size remains unchanged and integer value remains unchanged. Only the additional bit taken from the pad is utilized. Bugzilla reference: https://bugzilla.redhat.com/show_bug.cgi?id=838257 Signed-off-by: Tony Asleson <tasleson@redhat.com>
2015-05-04 22:51:41 +03:00
FIELD(LVS, lv, SNUM, "Maj", major, 3, int32, lv_major, "Persistent major number or -1 if not persistent.", 0)
FIELD(LVS, lv, SNUM, "Min", minor, 3, int32, lv_minor, "Persistent minor number or -1 if not persistent.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(LVS, lv, SIZ, "Rahead", lvid, 6, lvreadahead, lv_read_ahead, "Read ahead setting in current units.", 0)
FIELD(LVS, lv, SIZ, "LSize", size, 5, size64, lv_size, "Size of LV in current units.", 0)
report: lv_metadata_size, data_lv and metadata_lv also reports properties for cache pools
2015-04-10 15:55:28 +03:00
FIELD(LVS, lv, SIZ, "MSize", lvid, 6, lvmetadatasize, lv_metadata_size, "For thin and cache pools, the size of the LV that holds the metadata.", 0)
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(LVS, lv, NUM, "#Seg", lvid, 4, lvsegcount, seg_count, "Number of segments in LV.", 0)
FIELD(LVS, lv, STR, "Origin", lvid, 6, origin, origin, "For snapshots, the origin device of this LV.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(LVS, lv, SIZ, "OSize", lvid, 5, originsize, origin_size, "For snapshots, the size of the origin device of this LV.", 0)
cleanup: ancestors -> lv_ancestors, descendants -> lv_descendants Use "lv_" prefix as they're LV fields.
2015-04-24 15:19:23 +03:00
FIELD(LVS, lv, STR_LIST, "Ancestors", lvid, 12, lvancestors, lv_ancestors, "Ancestors of this LV.", 0)
FIELD(LVS, lv, STR_LIST, "Descendants", lvid, 12, lvdescendants, lv_descendants, "Descendants of this LV.", 0)
report: select: add support for percent selection
2014-06-09 18:23:45 +04:00
FIELD(LVS, lv, PCT, "Data%", lvid, 6, datapercent, data_percent, "For snapshot and thin pools and volumes, the percentage full if LV is active.", 0)
FIELD(LVS, lv, PCT, "Snap%", lvid, 6, snpercent, snap_percent, "For snapshots, the percentage full if LV is active.", 0)
FIELD(LVS, lv, PCT, "Meta%", lvid, 6, metadatapercent, metadata_percent, "For thin pools, the percentage of metadata full if LV is active.", 0)
FIELD(LVS, lv, PCT, "Cpy%Sync", lvid, 8, copypercent, copy_percent, "For RAID, mirrors and pvmove, current percentage in-sync.", 0)
FIELD(LVS, lv, PCT, "Cpy%Sync", lvid, 8, copypercent, sync_percent, "For RAID, mirrors and pvmove, current percentage in-sync.", 0)
reporting: tidy recent new fields Add underscores and prefixes to recently-added fields. (Might add more alias functionality in future.)
2013-07-19 04:30:02 +04:00
FIELD(LVS, lv, NUM, "Mismatches", lvid, 10, raidmismatchcount, raid_mismatch_count, "For RAID, number of mismatches found or repaired.", 0)
FIELD(LVS, lv, STR, "SyncAction", lvid, 10, raidsyncaction, raid_sync_action, "For RAID, the current synchronization action being performed.", 0)
FIELD(LVS, lv, NUM, "WBehind", lvid, 7, raidwritebehind, raid_write_behind, "For RAID1, the number of outstanding writes allowed to writemostly devices.", 0)
FIELD(LVS, lv, NUM, "MinSync", lvid, 7, raidminrecoveryrate, raid_min_recovery_rate, "For RAID1, the minimum recovery I/O load in kiB/sec/disk.", 0)
FIELD(LVS, lv, NUM, "MaxSync", lvid, 7, raidmaxrecoveryrate, raid_max_recovery_rate, "For RAID1, the maximum recovery I/O load in kiB/sec/disk.", 0)
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(LVS, lv, STR, "Move", lvid, 4, movepv, move_pv, "For pvmove, Source PV of temporary LV created by pvmove.", 0)
FIELD(LVS, lv, STR, "Convert", lvid, 7, convertlv, convert_lv, "For lvconvert, Name of temporary LV created by lvconvert.", 0)
FIELD(LVS, lv, STR, "Log", lvid, 3, loglv, mirror_log, "For mirrors, the LV holding the synchronisation log.", 0)
report: lv_metadata_size, data_lv and metadata_lv also reports properties for cache pools
2015-04-10 15:55:28 +03:00
FIELD(LVS, lv, STR, "Data", lvid, 4, datalv, data_lv, "For thin and cache pools, the LV holding the associated data.", 0)
FIELD(LVS, lv, STR, "Meta", lvid, 4, metadatalv, metadata_lv, "For thin and cache pools, the LV holding the associated metadata.", 0)
Thin add new display field for lvs New field Data% is able to display info about thin_pool, thin, snapshot and has generic meaning here. Simple Time/Host field are here to display host and time creation.
2012-01-19 19:34:32 +04:00
FIELD(LVS, lv, STR, "Pool", lvid, 4, poollv, pool_lv, "For thin volumes, the thin pool LV for this volume.", 0)
report: select: add DM_REPORT_FIELD_TYPE_STRING_LIST to make a difference between STRING and STRING_LIST The {pv,vg,lv,seg}_tags and lv_modules fields are reported as string lists using the new dm_report_field_string_list - so we just pass the list to the fn that takes care of reporting and item sorting itself.
2014-05-29 11:41:36 +04:00
FIELD(LVS, lv, STR_LIST, "LV Tags", tags, 7, tags, lv_tags, "Tags, if any.", 0)
reporting: tidy recent new fields Add underscores and prefixes to recently-added fields. (Might add more alias functionality in future.)
2013-07-19 04:30:02 +04:00
FIELD(LVS, lv, STR, "LProfile", lvid, 8, lvprofile, lv_profile, "Configuration profile attached to this LV.", 0)
Thin add new display field for lvs New field Data% is able to display info about thin_pool, thin, snapshot and has generic meaning here. Simple Time/Host field are here to display host and time creation.
2012-01-19 19:34:32 +04:00
FIELD(LVS, lv, STR, "Time", lvid, 26, lvtime, lv_time, "Creation time of the LV, if known", 0)
FIELD(LVS, lv, STR, "Host", lvid, 10, lvhost, lv_host, "Creation host of the LV, if known.", 0)
report: select: add DM_REPORT_FIELD_TYPE_STRING_LIST to make a difference between STRING and STRING_LIST The {pv,vg,lv,seg}_tags and lv_modules fields are reported as string lists using the new dm_report_field_string_list - so we just pass the list to the fn that takes care of reporting and item sorting itself.
2014-05-29 11:41:36 +04:00
FIELD(LVS, lv, STR_LIST, "Modules", lvid, 7, modules, lv_modules, "Kernel device-mapper modules required for this LV.", 0)
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
lvm2app: Add signed numerical property values Currently lvm2app properties have the following structure: typedef struct lvm_property_value { uint32_t is_settable:1; uint32_t is_string:1; uint32_t is_integer:1; uint32_t is_valid:1; uint32_t padding:28; union { const char *string; uint64_t integer; } value; } lvm_property_value_t; which assumes that numerical values were in the range of 0 to 2**64-1. However, some of the properties were 'signed', like LV major/minor numbers and some reserved values for properties that represent percentages. Thus when the values were retrieved they were in two's complement notation. So for a -1 major number the API user would get a value of 18446744073709551615. The API user could cast the returned value to an int64_t to handle this, but that requires the API developer to look at the source code and determine when it should be done. This change modifies the return property structure to: typedef struct lvm_property_value { uint32_t is_settable:1; uint32_t is_string:1; uint32_t is_integer:1; uint32_t is_valid:1; uint32_t is_signed:1; uint32_t padding:27; union { const char *string; uint64_t integer; int64_t signed_integer; } value; } lvm_property_value_t; With this addition the API user can interrogate that the value is numerical, (is_integer = 1) and subsequently check if it's signed (is_signed = 1) too. If signed, then the API developer should use the union's signed_integer to avoid casting. This change maintains backwards compatibility as the structure size remains unchanged and integer value remains unchanged. Only the additional bit taken from the pad is utilized. Bugzilla reference: https://bugzilla.redhat.com/show_bug.cgi?id=838257 Signed-off-by: Tony Asleson <tasleson@redhat.com>
2015-05-04 22:51:41 +03:00
FIELD(LVSINFO, lv, SNUM, "KMaj", lvid, 4, lvkmaj, lv_kernel_major, "Currently assigned major number or -1 if LV is not active.", 0)
FIELD(LVSINFO, lv, SNUM, "KMin", lvid, 4, lvkmin, lv_kernel_minor, "Currently assigned minor number or -1 if LV is not active.", 0)
refactor: use new LVSINFO report type for lv_kernel_{major,minor,read_ahead} field
2014-07-02 16:31:39 +04:00
FIELD(LVSINFO, lv, SIZ, "KRahead", lvid, 7, lvkreadahead, lv_kernel_read_ahead, "Currently-in-use read ahead setting in current units.", 0)
report: add separate fields for PV/VG/LV attributes Physical Volume Fields: pv_allocatable - Whether this device can be used for allocation. pv_exported - Whether this device is exported. pv_missing - Whether this device is missing in system. Volume Group Fields: vg_permissions - VG permissions. vg_extendable - Whether VG is extendable. vg_exported - Whether VG is exported. vg_partial - Whether VG is partial. vg_allocation_policy - VG allocation policy. vg_clustered - Whether VG is clustered. Logical Volume Fields: lv_volume_type - LV volume type. lv_initial_image_sync - Whether mirror/RAID images underwent initial resynchronization. lv_image_synced - Whether mirror/RAID image is synchronized. lv_merging - Whether snapshot LV is being merged to origin. lv_converting - Whether LV is being converted. lv_allocation_policy - LV allocation policy. lv_allocation_locked - Whether LV is locked against allocation changes. lv_fixed_minor - Whether LV has fixed minor number assigned. lv_merge_failed - Whether snapshot merge failed. lv_snapshot_invalid - Whether snapshot LV is invalid. lv_target_type - Kernel target type the LV is related to. lv_health_status - LV health status. lv_skip_activation - Whether LV is skipped on activation. Logical Volume Info Fields lv_permissions - LV permissions. lv_suspended - Whether LV is suspended. lv_live_table - Whether LV has live table present. lv_inactive_table - Whether LV has inactive table present. lv_device_open - Whether LV device is open.
2014-07-02 13:09:14 +04:00
FIELD(LVSINFO, lv, STR, "LPerms", lvid, 8, lvpermissions, lv_permissions, "LV permissions.", 0)
report: 'whether' -> 'set if' in field description
2014-07-09 15:41:25 +04:00
FIELD(LVSINFO, lv, BIN, "Suspended", lvid, 10, lvsuspended, lv_suspended, "Set if LV is suspended.", 0)
FIELD(LVSINFO, lv, BIN, "LiveTable", lvid, 20, lvlivetable, lv_live_table, "Set if LV has live table present.", 0)
FIELD(LVSINFO, lv, BIN, "InactiveTable", lvid, 20, lvinactivetable, lv_inactive_table, "Set if LV has inactive table present.", 0)
FIELD(LVSINFO, lv, BIN, "DevOpen", lvid, 10, lvdeviceopen, lv_device_open, "Set if LV device is open.", 0)
refactor: use new LVSINFO report type for lv_kernel_{major,minor,read_ahead} field
2014-07-02 16:31:39 +04:00
report: add cache device status fields New reporting fields related to cache device status: - cache_total_blocks - cache_used_blocks - cache_dirty_blocks - cache_read_hits - cache_read_misses - cache_write_hits - cache_write_misses
2014-10-24 15:39:56 +04:00
FIELD(LVSSTATUS, lv, NUM, "CacheTotalBlocks", lvid, 16, cache_total_blocks, cache_total_blocks, "Total cache blocks.", 0)
FIELD(LVSSTATUS, lv, NUM, "CacheUsedBlocks", lvid, 16, cache_used_blocks, cache_used_blocks, "Used cache blocks.", 0)
FIELD(LVSSTATUS, lv, NUM, "CacheDirtyBlocks", lvid, 16, cache_dirty_blocks, cache_dirty_blocks, "Dirty cache blocks.", 0)
FIELD(LVSSTATUS, lv, NUM, "CacheReadHits", lvid, 16, cache_read_hits, cache_read_hits, "Cache read hits.", 0)
FIELD(LVSSTATUS, lv, NUM, "CacheReadMisses", lvid, 16, cache_read_misses, cache_read_misses, "Cache read misses.", 0)
FIELD(LVSSTATUS, lv, NUM, "CacheWriteHits", lvid, 16, cache_write_hits, cache_write_hits, "Cache write hits.", 0)
FIELD(LVSSTATUS, lv, NUM, "CacheWriteMisses", lvid, 16, cache_write_misses, cache_write_misses, "Cache write misses.", 0)
report: use same info also for lv_attr Recently the single 'status' code has been used for number of cache features. Extend the API a little bit to allow usage also for lv_attr_dup. As the function itself is used in lvm2api - add a new function: lv_attr_dup_with_info_and_seg_status() that is able to use grabbed info & status information. report_init() is now using directly passed lvdm struct pointer which holds the infomation whether lv_info() was correctly obtained or there was some error when trying to read it. Move 'healt' attribute to status. TODO convert raid function to use the already known status.
2015-01-20 15:14:16 +03:00
FIELD(LVSSTATUS, lv, STR, "Health", lvid, 15, lvhealthstatus, lv_health_status, "LV health status.", 0)
report: add cache device status fields New reporting fields related to cache device status: - cache_total_blocks - cache_used_blocks - cache_dirty_blocks - cache_read_hits - cache_read_misses - cache_write_hits - cache_write_misses
2014-10-24 15:39:56 +04:00
report: Adapt _pvfmt_disp to label-based reporting.
2013-07-29 18:00:40 +04:00
FIELD(LABEL, label, STR, "Fmt", type, 3, pvfmt, pv_fmt, "Type of metadata.", 0)
report: Make PV UUID into a "label" type field.
2013-07-29 21:15:31 +04:00
FIELD(LABEL, label, STR, "PV UUID", type, 38, pvuuid, pv_uuid, "Unique identifier.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(LABEL, label, SIZ, "DevSize", dev, 7, devsize, dev_size, "Size of underlying device in current units.", 0)
report: Make dev_size and dev_name columns' type "label".
2013-07-29 21:05:28 +04:00
FIELD(LABEL, label, STR, "PV", dev, 10, dev_name, pv_name, "Name.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(LABEL, label, SIZ, "PMdaFree", type, 9, pvmdafree, pv_mda_free, "Free metadata area space on this device in current units.", 0)
FIELD(LABEL, label, SIZ, "PMdaSize", type, 9, pvmdasize, pv_mda_size, "Size of smallest metadata area on this device in current units.", 0)
Separate PV label attributes which do not need parse metadata when reporting. When reporting explicitly label attributes (pv_uuid for example), we do not need to read metadata. This patch separate the label fileds and removes scan_vgs_for_pvs in process_each_pv() if not needed. (There should be no user visible change in output.)
2009-02-09 12:45:49 +03:00
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(PVS, pv, NUM, "1st PE", pe_start, 7, size64, pe_start, "Offset to the start of data on the underlying device.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(PVS, pv, SIZ, "PSize", id, 5, pvsize, pv_size, "Size of PV in current units.", 0)
FIELD(PVS, pv, SIZ, "PFree", id, 5, pvfree, pv_free, "Total amount of unallocated space in current units.", 0)
FIELD(PVS, pv, SIZ, "Used", id, 4, pvused, pv_used, "Total amount of allocated space in current units.", 0)
Add {pv|vg|lv}_attr_dup() functions and refactor 'disp' functions. Move the creating of the 'attr' strings into a common function so they can be called from the 'disp' functions as well as the new 'get' property functions. Add "_dup" suffix to indicate memory is allocated. Refactor pvstatus_disp to take pv argument and call pv_attr_dup().
2010-09-30 17:52:55 +04:00
FIELD(PVS, pv, STR, "Attr", id, 4, pvstatus, pv_attr, "Various attributes - see man page.", 0)
report: 'whether' -> 'set if' in field description
2014-07-09 15:41:25 +04:00
FIELD(PVS, pv, BIN, "Allocatable", id, 10, pvallocatable, pv_allocatable, "Set if this device can be used for allocation.", 0)
FIELD(PVS, pv, BIN, "Exported", id, 10, pvexported, pv_exported, "Set if this device is exported.", 0)
FIELD(PVS, pv, BIN, "Missing", id, 10, pvmissing, pv_missing, "Set if this device is missing in system.", 0)
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(PVS, pv, NUM, "PE", pe_count, 3, uint32, pv_pe_count, "Total number of Physical Extents.", 0)
FIELD(PVS, pv, NUM, "Alloc", pe_alloc_count, 5, uint32, pv_pe_alloc_count, "Total number of allocated Physical Extents.", 0)
report: select: add DM_REPORT_FIELD_TYPE_STRING_LIST to make a difference between STRING and STRING_LIST The {pv,vg,lv,seg}_tags and lv_modules fields are reported as string lists using the new dm_report_field_string_list - so we just pass the list to the fn that takes care of reporting and item sorting itself.
2014-05-29 11:41:36 +04:00
FIELD(PVS, pv, STR_LIST, "PV Tags", tags, 7, tags, pv_tags, "Tags, if any.", 0)
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(PVS, pv, NUM, "#PMda", id, 5, pvmdas, pv_mda_count, "Number of metadata areas on this device.", 0)
FIELD(PVS, pv, NUM, "#PMdaUse", id, 8, pvmdasused, pv_mda_used_count, "Number of metadata areas in use on this device.", 0)
report: define ba_start, vg_free and seg_start fields as DM_REPORT_FIELD_TYPE_SIZE instead of DM_REPORT_FIELD_TYPE_NUM This makes a difference when using selection criteria based on these fields - if those fields are defined as DM_REPORT_FIELD_TYPE_SIZE (in contrast to DM_REPORT_FIELD_TYPE_NUMBER), units are also recognize in selection clause. For example: $ lvs -o+seg_start vg1/lv2 LV VG Attr LSize Start lv2 vg1 -wi-a----- 12.00m 0 lv2 vg1 -wi-a----- 12.00m 8.00m Before this patch: $ lvs -o+seg_start --select 'seg_start=8m' Found size unit specifier but numeric value expected for selection field seg_start. Selection syntax error at 'seg_start=8m'. Use 'help' for selection to get more help. With this patch applied: $lvs -o+seg_start --select 'seg_start=8m' LV VG Attr LSize Start lv2 vg1 -wi-a----- 12.00m 8.00m (the same applies for ba_start and vg_free fields)
2015-02-11 15:57:18 +03:00
FIELD(PVS, pv, SIZ, "BA start", ba_start, 8, size64, pv_ba_start, "Offset to the start of PV Bootloader Area on the underlying device in current units.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(PVS, pv, SIZ, "BA size", ba_size, 7, size64, pv_ba_size, "Size of PV Bootloader Area in current units.", 0)
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(VGS, vg, STR, "Fmt", cmd, 3, vgfmt, vg_fmt, "Type of metadata.", 0)
FIELD(VGS, vg, STR, "VG UUID", id, 38, uuid, vg_uuid, "Unique identifier.", 0)
FIELD(VGS, vg, STR, "VG", name, 4, string, vg_name, "Name.", 0)
FIELD(VGS, vg, STR, "Attr", cmd, 5, vgstatus, vg_attr, "Various attributes - see man page.", 0)
report: add separate fields for PV/VG/LV attributes Physical Volume Fields: pv_allocatable - Whether this device can be used for allocation. pv_exported - Whether this device is exported. pv_missing - Whether this device is missing in system. Volume Group Fields: vg_permissions - VG permissions. vg_extendable - Whether VG is extendable. vg_exported - Whether VG is exported. vg_partial - Whether VG is partial. vg_allocation_policy - VG allocation policy. vg_clustered - Whether VG is clustered. Logical Volume Fields: lv_volume_type - LV volume type. lv_initial_image_sync - Whether mirror/RAID images underwent initial resynchronization. lv_image_synced - Whether mirror/RAID image is synchronized. lv_merging - Whether snapshot LV is being merged to origin. lv_converting - Whether LV is being converted. lv_allocation_policy - LV allocation policy. lv_allocation_locked - Whether LV is locked against allocation changes. lv_fixed_minor - Whether LV has fixed minor number assigned. lv_merge_failed - Whether snapshot merge failed. lv_snapshot_invalid - Whether snapshot LV is invalid. lv_target_type - Kernel target type the LV is related to. lv_health_status - LV health status. lv_skip_activation - Whether LV is skipped on activation. Logical Volume Info Fields lv_permissions - LV permissions. lv_suspended - Whether LV is suspended. lv_live_table - Whether LV has live table present. lv_inactive_table - Whether LV has inactive table present. lv_device_open - Whether LV device is open.
2014-07-02 13:09:14 +04:00
FIELD(VGS, vg, STR, "VPerms", cmd, 10, vgpermissions, vg_permissions, "VG permissions.", 0)
report: 'whether' -> 'set if' in field description
2014-07-09 15:41:25 +04:00
FIELD(VGS, vg, BIN, "Extendable", cmd, 10, vgextendable, vg_extendable, "Set if VG is extendable.", 0)
FIELD(VGS, vg, BIN, "Exported", cmd, 10, vgexported, vg_exported, "Set if VG is exported.", 0)
FIELD(VGS, vg, BIN, "Partial", cmd, 10, vgpartial, vg_partial, "Set if VG is partial.", 0)
report: add separate fields for PV/VG/LV attributes Physical Volume Fields: pv_allocatable - Whether this device can be used for allocation. pv_exported - Whether this device is exported. pv_missing - Whether this device is missing in system. Volume Group Fields: vg_permissions - VG permissions. vg_extendable - Whether VG is extendable. vg_exported - Whether VG is exported. vg_partial - Whether VG is partial. vg_allocation_policy - VG allocation policy. vg_clustered - Whether VG is clustered. Logical Volume Fields: lv_volume_type - LV volume type. lv_initial_image_sync - Whether mirror/RAID images underwent initial resynchronization. lv_image_synced - Whether mirror/RAID image is synchronized. lv_merging - Whether snapshot LV is being merged to origin. lv_converting - Whether LV is being converted. lv_allocation_policy - LV allocation policy. lv_allocation_locked - Whether LV is locked against allocation changes. lv_fixed_minor - Whether LV has fixed minor number assigned. lv_merge_failed - Whether snapshot merge failed. lv_snapshot_invalid - Whether snapshot LV is invalid. lv_target_type - Kernel target type the LV is related to. lv_health_status - LV health status. lv_skip_activation - Whether LV is skipped on activation. Logical Volume Info Fields lv_permissions - LV permissions. lv_suspended - Whether LV is suspended. lv_live_table - Whether LV has live table present. lv_inactive_table - Whether LV has inactive table present. lv_device_open - Whether LV device is open.
2014-07-02 13:09:14 +04:00
FIELD(VGS, vg, STR, "AllocPol", cmd, 10, vgallocationpolicy, vg_allocation_policy, "VG allocation policy.", 0)
report: 'whether' -> 'set if' in field description
2014-07-09 15:41:25 +04:00
FIELD(VGS, vg, BIN, "Clustered", cmd, 10, vgclustered, vg_clustered, "Set if VG is clustered.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(VGS, vg, SIZ, "VSize", cmd, 5, vgsize, vg_size, "Total size of VG in current units.", 0)
report: define ba_start, vg_free and seg_start fields as DM_REPORT_FIELD_TYPE_SIZE instead of DM_REPORT_FIELD_TYPE_NUM This makes a difference when using selection criteria based on these fields - if those fields are defined as DM_REPORT_FIELD_TYPE_SIZE (in contrast to DM_REPORT_FIELD_TYPE_NUMBER), units are also recognize in selection clause. For example: $ lvs -o+seg_start vg1/lv2 LV VG Attr LSize Start lv2 vg1 -wi-a----- 12.00m 0 lv2 vg1 -wi-a----- 12.00m 8.00m Before this patch: $ lvs -o+seg_start --select 'seg_start=8m' Found size unit specifier but numeric value expected for selection field seg_start. Selection syntax error at 'seg_start=8m'. Use 'help' for selection to get more help. With this patch applied: $lvs -o+seg_start --select 'seg_start=8m' LV VG Attr LSize Start lv2 vg1 -wi-a----- 12.00m 8.00m (the same applies for ba_start and vg_free fields)
2015-02-11 15:57:18 +03:00
FIELD(VGS, vg, SIZ, "VFree", cmd, 5, vgfree, vg_free, "Total amount of free space in current units.", 0)
lvm1: Reenable sys ID. Move the lvm1 sys ID into vg->lvm1_system_id and reenable the #if 0 LVM1 code. Still display the new-style system ID in the same reporting field, though, as only one can be set. Add a format feature flag FMT_SYSTEM_ON_PVS for LVM1 and disallow access to LVM1 VGs if a new-style system ID has been set. Treat the new vg->system_id as const.
2015-02-24 02:03:52 +03:00
FIELD(VGS, vg, STR, "SYS ID", cmd, 6, vgsystemid, vg_sysid, "System ID of the VG indicating which host owns it.", 0)
FIELD(VGS, vg, STR, "System ID", cmd, 9, vgsystemid, vg_systemid, "System ID of the VG indicating which host owns it.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(VGS, vg, SIZ, "Ext", extent_size, 3, size32, vg_extent_size, "Size of Physical Extents in current units.", 0)
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(VGS, vg, NUM, "#Ext", extent_count, 4, uint32, vg_extent_count, "Total number of Physical Extents.", 0)
FIELD(VGS, vg, NUM, "Free", free_count, 4, uint32, vg_free_count, "Total number of unallocated Physical Extents.", 0)
FIELD(VGS, vg, NUM, "MaxLV", max_lv, 5, uint32, max_lv, "Maximum number of LVs allowed in VG or 0 if unlimited.", 0)
FIELD(VGS, vg, NUM, "MaxPV", max_pv, 5, uint32, max_pv, "Maximum number of PVs allowed in VG or 0 if unlimited.", 0)
FIELD(VGS, vg, NUM, "#PV", pv_count, 3, uint32, pv_count, "Number of PVs.", 0)
FIELD(VGS, vg, NUM, "#LV", cmd, 3, lvcount, lv_count, "Number of LVs.", 0)
FIELD(VGS, vg, NUM, "#SN", cmd, 3, snapcount, snap_count, "Number of snapshots.", 0)
FIELD(VGS, vg, NUM, "Seq", seqno, 3, uint32, vg_seqno, "Revision number of internal metadata. Incremented whenever it changes.", 0)
report: select: add DM_REPORT_FIELD_TYPE_STRING_LIST to make a difference between STRING and STRING_LIST The {pv,vg,lv,seg}_tags and lv_modules fields are reported as string lists using the new dm_report_field_string_list - so we just pass the list to the fn that takes care of reporting and item sorting itself.
2014-05-29 11:41:36 +04:00
FIELD(VGS, vg, STR_LIST, "VG Tags", tags, 7, tags, vg_tags, "Tags, if any.", 0)
reporting: tidy recent new fields Add underscores and prefixes to recently-added fields. (Might add more alias functionality in future.)
2013-07-19 04:30:02 +04:00
FIELD(VGS, vg, STR, "VProfile", cmd, 8, vgprofile, vg_profile, "Configuration profile attached to this VG.", 0)
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(VGS, vg, NUM, "#VMda", cmd, 5, vgmdas, vg_mda_count, "Number of metadata areas on this VG.", 0)
FIELD(VGS, vg, NUM, "#VMdaUse", cmd, 8, vgmdasused, vg_mda_used_count, "Number of metadata areas in use on this VG.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(VGS, vg, SIZ, "VMdaFree", cmd, 9, vgmdafree, vg_mda_free, "Free metadata area space for this VG in current units.", 0)
FIELD(VGS, vg, SIZ, "VMdaSize", cmd, 9, vgmdasize, vg_mda_size, "Size of smallest metadata area for this VG in current units.", 0)
Add generic infrastructure to internal library to 'set' a property. Similar to 'get' property internal functions. Add specific 'set' function for vg_mda_copies. Signed-off-by: Dave Wysochanski <wysochanski@pobox.com> Reviewed-by: Petr Rockai <prockai@redhat.com>
2010-11-17 22:15:10 +03:00
FIELD(VGS, vg, NUM, "#VMdaCps", cmd, 8, vgmdacopies, vg_mda_copies, "Target number of in use metadata areas in the VG.", 1)
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
pre-release
2014-08-26 19:34:14 +04:00
FIELD(SEGS, seg, STR, "Type", list, 4, segtype, segtype, "Type of LV segment.", 0)
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(SEGS, seg, NUM, "#Str", area_count, 4, uint32, stripes, "Number of stripes or mirror legs.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(SEGS, seg, SIZ, "Stripe", stripe_size, 6, size32, stripesize, "For stripes, amount of data placed on one device before switching to the next.", 0)
FIELD(SEGS, seg, SIZ, "Stripe", stripe_size, 6, size32, stripe_size, "For stripes, amount of data placed on one device before switching to the next.", 0)
FIELD(SEGS, seg, SIZ, "Region", region_size, 6, size32, regionsize, "For mirrors, the unit of data copied when synchronising devices.", 0)
FIELD(SEGS, seg, SIZ, "Region", region_size, 6, size32, region_size, "For mirrors, the unit of data copied when synchronising devices.", 0)
FIELD(SEGS, seg, SIZ, "Chunk", list, 5, chunksize, chunksize, "For snapshots, the unit of data used when tracking changes.", 0)
FIELD(SEGS, seg, SIZ, "Chunk", list, 5, chunksize, chunk_size, "For snapshots, the unit of data used when tracking changes.", 0)
Thin add new display field for lvs New field Data% is able to display info about thin_pool, thin, snapshot and has generic meaning here. Simple Time/Host field are here to display host and time creation.
2012-01-19 19:34:32 +04:00
FIELD(SEGS, seg, NUM, "#Thins", list, 4, thincount, thin_count, "For thin pools, the number of thin volumes in this pool.", 0)
thin: fix property discard for lvm2api Discards property is string and may have these values: ignore, nopassdown, passdown
2012-11-27 14:02:49 +04:00
FIELD(SEGS, seg, STR, "Discards", list, 8, discards, discards, "For thin pools, how discards are handled.", 0)
cache: include cache mode in vg metadata and display The cache mode of a new cache pool is always explicitly included in the vg metadata. If a cache mode is not specified on the command line, the cache mode is taken from lvm.conf allocation/cache_pool_cachemode, which defaults to "writethrough". The cache mode can be displayed with lvs -o+cachemode.
2014-10-02 01:06:01 +04:00
FIELD(SEGS, seg, STR, "Cachemode", list, 9, cachemode, cachemode, "For cache pools, how writes are cached.", 0)
report: report LV's zero field as binary field Like other binary fields we already have: $ lvs -o name,zero vg/lvx vg/pool vg/pool1 LV Zero lvx unknown pool pool1 zero $ lvs -o name,zero vg/lvx vg/pool vg/pool1 --binary LV Zero lvx -1 pool 0 pool1 1
2014-07-10 17:23:56 +04:00
FIELD(SEGS, seg, BIN, "Zero", list, 4, thinzero, zero, "For thin pools, if zeroing is enabled.", 0)
Thin add new display field for lvs New field Data% is able to display info about thin_pool, thin, snapshot and has generic meaning here. Simple Time/Host field are here to display host and time creation.
2012-01-19 19:34:32 +04:00
FIELD(SEGS, seg, NUM, "TransId", list, 4, transactionid, transaction_id, "For thin pools, the transaction id.", 0)
thin: report thin device id Support lvs -o+thin_id to report thin device id. This device_id is connection between kernel and lvm2 user space thin metadata.
2013-11-11 13:05:45 +04:00
FIELD(SEGS, seg, NUM, "ThId", list, 4, thinid, thin_id, "For thin volume, the thin device id.", 0)
report: define ba_start, vg_free and seg_start fields as DM_REPORT_FIELD_TYPE_SIZE instead of DM_REPORT_FIELD_TYPE_NUM This makes a difference when using selection criteria based on these fields - if those fields are defined as DM_REPORT_FIELD_TYPE_SIZE (in contrast to DM_REPORT_FIELD_TYPE_NUMBER), units are also recognize in selection clause. For example: $ lvs -o+seg_start vg1/lv2 LV VG Attr LSize Start lv2 vg1 -wi-a----- 12.00m 0 lv2 vg1 -wi-a----- 12.00m 8.00m Before this patch: $ lvs -o+seg_start --select 'seg_start=8m' Found size unit specifier but numeric value expected for selection field seg_start. Selection syntax error at 'seg_start=8m'. Use 'help' for selection to get more help. With this patch applied: $lvs -o+seg_start --select 'seg_start=8m' LV VG Attr LSize Start lv2 vg1 -wi-a----- 12.00m 8.00m (the same applies for ba_start and vg_free fields)
2015-02-11 15:57:18 +03:00
FIELD(SEGS, seg, SIZ, "Start", list, 5, segstart, seg_start, "Offset within the LV to the start of the segment in current units.", 0)
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(SEGS, seg, NUM, "Start", list, 5, segstartpe, seg_start_pe, "Offset within the LV to the start of the segment in physical extents.", 0)
report: select: add DM_REPORT_FIELD_TYPE_SIZE to make a difference between NUMBER and SIZE This makes it easier to check against the fields (following patches for report selection) and check whether size units are allowed or not with the field value.
2014-05-29 11:37:22 +04:00
FIELD(SEGS, seg, SIZ, "SSize", list, 5, segsize, seg_size, "Size of segment in current units.", 0)
FIELD(SEGS, seg, SIZ, "SSize", list, 5, segsizepe, seg_size_pe, "Size of segment in physical extents.", 0)
report: select: add DM_REPORT_FIELD_TYPE_STRING_LIST to make a difference between STRING and STRING_LIST The {pv,vg,lv,seg}_tags and lv_modules fields are reported as string lists using the new dm_report_field_string_list - so we just pass the list to the fn that takes care of reporting and item sorting itself.
2014-05-29 11:41:36 +04:00
FIELD(SEGS, seg, STR_LIST, "Seg Tags", tags, 8, tags, seg_tags, "Tags, if any.", 0)
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(SEGS, seg, STR, "PE Ranges", list, 9, peranges, seg_pe_ranges, "Ranges of Physical Extents of underlying devices in command line format.", 0)
FIELD(SEGS, seg, STR, "Devices", list, 7, devices, devices, "Underlying devices used with starting extent numbers.", 0)
reporting: tidy recent new fields Add underscores and prefixes to recently-added fields. (Might add more alias functionality in future.)
2013-07-19 04:30:02 +04:00
FIELD(SEGS, seg, STR, "Monitor", list, 7, segmonitor, seg_monitor, "Dmeventd monitoring status of the segment.", 0)
report: Add cache_policy and cache_settings (LV) segment fields.
2014-12-15 22:48:05 +03:00
FIELD(SEGS, seg, STR, "Cache Policy", list, 12, cache_policy, cache_policy, "The cache policy (cached segments only).", 0)
FIELD(SEGS, seg, STR_LIST, "Cache Settings", list, 14, cache_settings, cache_settings, "Cache settings/parameters (cached segments only).", 0)
Initial pv_segment code.
2005-04-20 00:58:25 +04:00
Remove explicit double quotes from columns.h 'id' entries. The 'id' entries in columns.h are the report field names. Since these are unique, we'd like to use them in generation of 'get' / 'set' functions. As a step towards using them for this purpose, remove the explicit double quotes and use the macro '#' character to add the double quotes back when placing them into the '_fields' array 'id' member.
2010-08-20 16:44:17 +04:00
FIELD(PVSEGS, pvseg, NUM, "Start", pe, 5, uint32, pvseg_start, "Physical Extent number of start of segment.", 0)
FIELD(PVSEGS, pvseg, NUM, "SSize", len, 5, uint32, pvseg_size, "Number of extents in segment.", 0)
Allow for specification of major number as well as minor.
2003-04-02 23:14:43 +04:00
/* *INDENT-ON* */
Copy Permalink