lvchange(8) describes the following available arguments for -a: -a, --available y/n/ey/en/ly/ln However, the description has an error, mentioning "-ae" which doesn't exist: If clustered locking is enabled, -ae will activate exclusively on one node and -aly will activate only on the local node. To deactivate only on the local node use -aln. Logical volumes with single-host snapshots are always activated exclusively because they can only be used on one node at once. It's probably -aey or -aen, but not -ae.
Agreed the man pg should be consistent. Note though that 'ae' is equivalent to 'aey' (and 'aye' for that matter) in the code: int yes_no_excl_arg(struct cmd_context *cmd __attribute((unused)), struct arg *a) { a->sign = SIGN_NONE; a->percent = PERCENT_NONE; if (!strcmp(a->value, "e") || !strcmp(a->value, "ey") || !strcmp(a->value, "ye")) { a->i_value = CHANGE_AE; a->ui_value = CHANGE_AE; } else if (!strcmp(a->value, "y")) { a->i_value = CHANGE_AY; a->ui_value = CHANGE_AY; } else if (!strcmp(a->value, "n") || !strcmp(a->value, "en") || !strcmp(a->value, "ne")) { a->i_value = CHANGE_AN; a->ui_value = CHANGE_AN; } else if (!strcmp(a->value, "ln") || !strcmp(a->value, "nl")) { a->i_value = CHANGE_ALN; a->ui_value = CHANGE_ALN; } else if (!strcmp(a->value, "ly") || !strcmp(a->value, "yl")) { a->i_value = CHANGE_ALY; a->ui_value = CHANGE_ALY; }
Now upstream will be in next releases (2.02.38+).
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Commited to CVS in version lvm2-2.02.39-1.el5.
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. http://rhn.redhat.com/errata/RHBA-2009-0179.html