diff options
| author | Dave Wysochanski <dwysocha@redhat.com> | 2009-10-05 20:02:48 +0000 |
|---|---|---|
| committer | Dave Wysochanski <dwysocha@redhat.com> | 2009-10-05 20:02:48 +0000 |
| commit | 29123aa652cd67d542c428b154384d74dbf8087b (patch) | |
| tree | 380d8ece76c75c1cf60833911366ee958febac3a /tools/vgextend.c | |
| parent | acb4073eedfe64c5ee8a4315009a3d7415976530 (diff) | |
| download | lvm2-29123aa652cd67d542c428b154384d74dbf8087b.tar.gz lvm2-29123aa652cd67d542c428b154384d74dbf8087b.tar.xz lvm2-29123aa652cd67d542c428b154384d74dbf8087b.zip | |
Add pvcreate_params to vg_extend.
Another refactoring for implicit pvcreate support. We need to get
the pvcreate parameters somehow to the vg_extend routine. Options
seemed to be:
1. Attach the parameters to struct volume_group. I personally
did not like this idea in most cases, though one could make an
agrument why it might be ok at least for some of the parameters
(e.g. metadatacopies).
2. Pass them in to the extend routine. This second route seemed
to be the best approach given the constraints.
Future patches will parse the command line and fill in the actual
values for the pvcreate_single call.
Should be no functional change.
Diffstat (limited to 'tools/vgextend.c')
| -rw-r--r-- | tools/vgextend.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/vgextend.c b/tools/vgextend.c index b659492e..9fa7d317 100644 --- a/tools/vgextend.c +++ b/tools/vgextend.c @@ -54,7 +54,7 @@ int vgextend(struct cmd_context *cmd, int argc, char **argv) goto_bad; /* extend vg */ - if (!vg_extend(vg, argc, argv)) + if (!vg_extend(vg, argc, argv, NULL)) goto_bad; /* ret > 0 */ |