Description of problem:
The LVM2 administrators guide incorrectly states that the stripe size of LVM2 volumes is limited to a power of 2 between 4kB and 512kB (p35). This is also present in the online version:

http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/pdf/Cluster_Logical_Volume_Manager.pdf

--- snip ---
4.1.2. Creating Striped Volumes
The stripe size should be tuned to a power of 2 between 4kB and
512kB, and matched to the application's I/O that is using the
striped volume. The -I argument of the lvcreate command specifies
the stripe size in kilobytes.
--- snip ---

This is only the case for the LVM1 binary metadata format. The LVM2 text VG format declares the format flag FMT_UNLIMITED_STRIPESIZE and is not subject to this restriction.

See the following code which enforces the check for other metadata formats (but not LVM2):

tools/lvcreate.c:_lvcreate():
535         if (lp->stripes > 1 &&
536             !(vg->fid->fmt->features & FMT_UNLIMITED_STRIPESIZE) &&
537             (lp->stripe_size > STRIPE_SIZE_MAX)) {
538                 log_error("Stripe size may not exceed %s",
539                           display_size(cmd, (uint64_t) STRIPE_SIZE_MAX));
540                 return 0;
541         }

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Read the doc :)
  
Actual results:
Limits described apply to LVM1 not LVM2 metadata.

Expected results:
Documentation should either document LVM2 capabilities or make it clear that this restriction is only for legacy LVM1 volume groups.