Escalated to Bugzilla from IssueTracker
man page for lvscan does not describe possible values in the output
fields. In particular, the "state". In this case, the customer wanted to
know what else besides "ACTIVE" would be a possible value.
For more complete information, consider using the 'lvs' tool instead, which is better documented:
The lv_attr bits are:
1 Volume type: (m)irrored, (M)irrored without initial sync,
(o)rigin, (p)vmove, (s)napshot, invalid (S)napshot,
(v)irtual, mirror (i)mage, mirror (I)mage out-of-sync, under
2 Permissions: (w)riteable, (r)ead-only
3 Allocation policy: (c)ontiguous, c(l)ing, (n)ormal,
(a)nywhere, (i)nherited This is capitalised if the volume is
currently locked against allocation changes, for example dur-
ing pvmove (8).
4 fixed (m)inor
5 State: (a)ctive, (s)uspended, (I)nvalid snapshot, invalid
(S)uspended snapshot, mapped (d)evice present without tables,
mapped device present with (i)nactive table
6 device (o)pen
Updated in 2.02.82.
Fix verified in the latest rpms:
" The output consists of one line for each Logical Volume indicating whether or not it is active, a snapshot or origin, the size of the device and its allocation policy. Use lvs(8) or lvdisplay(8) to obtain more-comprehensive information about the Logical Volumes."
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.