Bug#586957: lvm2: miscellaneous improvements for the lvm(8) manpage

[Alasdair G Kergon]

On Thu, Jun 24, 2010 at 12:47:49AM +0200, Christoph Anton Mitterer wrote:
> It seems that the current "Where a list of VGs is required but is left empty, a
> list  of  all VGs will be substituted." is also true for LVs (checked it with
> lvdisplay, which seems to lists all LVs).

Yes
 
> - Also clarifies, that @ is only used
> when referencing tags, not when setting them (i.e. that it's just part of the
> string name).

?
You should always be able to use @ to indicate a tag.
It's optional in places where there's no ambiguity.
 
 

> 1) Should we explicitly mention, that VG/LV names as well as tags are case-
> sensitive (or is A-Z a-z) enough.
 
No harm in doing that - I just assumed people would assume that...

> 2) Regarding --alloc
> "The cling policy places new extents on the same physical volume as existing
> extents in the same stripe of the Logical Volume."

Example:
Given A1 A2  and B1 B2  as two stripes of two extents, and space to be
allocated when extending:  A4 and B4,   cling ensures you get A1 A2 A4  and  B1
B2 B4  instead of A1 A2 B4  and  B1 B2 A4.

"New extent (A4) on the same PV as existing extents (A1 A2) in the same stripe."

 
> AFAIK: "For  metadata in  LVM2  format, the stripe size may be a larger power
> of 2 but must not exceed the physical extent size."
> So it's always that _one_ extent can be divided in one or more stripes, but
> _not_ that _one_ stripe can have several extents, right?
 
"one stripe can have several extents" is imprecise to me.

Alasdair