shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-10-28 03:27:58 +03:00
Code Releases Activity
1e1c2769a7
lvm2/lib/report/columns.h

140 lines
13 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
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)
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, "Attr", lvid, 4, lvstatus, lv_attr, "Various attributes - see man page.", 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)
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, "Maj", major, 3, int32, lv_major, "Persistent major number or -1 if not persistent.", 0)
FIELD(LVS, lv, NUM, "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)
report: fix report field type for lv_kernel_major/minor Should be defined as numeric field, not string field.
2014-05-30 19:23:54 +04:00
FIELD(LVS, lv, NUM, "KMaj", lvid, 4, lvkmaj, lv_kernel_major, "Currently assigned major number or -1 if LV is not active.", 0)
FIELD(LVS, lv, NUM, "KMin", lvid, 4, lvkmin, lv_kernel_minor, "Currently assigned minor number or -1 if LV is not active.", 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, "KRahead", lvid, 7, lvkreadahead, lv_kernel_read_ahead, "Currently-in-use read ahead setting in current units.", 0)
FIELD(LVS, lv, SIZ, "LSize", size, 5, size64, lv_size, "Size of LV in current units.", 0)
FIELD(LVS, lv, SIZ, "MSize", lvid, 6, lvmetadatasize, lv_metadata_size, "For thin 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)
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)
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, "Data", lvid, 4, datalv, data_lv, "For thin pools, the LV holding the associated data.", 0)
FIELD(LVS, lv, STR, "Meta", lvid, 4, metadatalv, metadata_lv, "For thin pools, the LV holding the associated metadata.", 0)
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
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)
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)
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(PVS, pv, NUM, "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: 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)
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, "VFree", cmd, 5, vgfree, vg_free, "Total amount of free space in current units.", 0)
FIELD(VGS, vg, STR, "SYS ID", system_id, 6, string, vg_sysid, "System ID indicating when and where it was created.", 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
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, "Type", list, 4, segtype, segtype, "Type of LV segment.", 0)
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)
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, "Zero", list, 4, thinzero, zero, "For thin pools, if zeroing is enabled.", 0)
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)
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, segstart, seg_start, "Offset within the LV to the start of the segment in current units.", 0)
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)
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