Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lvcreate: don't put VG name in LV name #176

Closed
ggzengel opened this issue Aug 24, 2020 · 2 comments
Closed

lvcreate: don't put VG name in LV name #176

ggzengel opened this issue Aug 24, 2020 · 2 comments

Comments

@ggzengel
Copy link

Wrong usage:

# lvcreate --size 7204k -n VG1/vm-107-disk-2.meta_00000 -y -m 1 /dev/nvme0n1 /dev/nvme1n1
  Inconsistent volume group names given: "VG1" and "nvme0n1"
  Run `lvcreate --help' for more information.

Right usage:

# lvcreate --size 7204k VG1 -n vm-107-disk-2.meta_00000 -y -m 1 /dev/nvme0n1 /dev/nvme1n1
  Rounding up size to full physical extent 8.00 MiB
  Logical volume "vm-107-disk-2.meta_00000" created.

I use this to put the meta data to the Intel Optane as RAID1:
linstor sp sp px1 zfs_12_meta StorDriver/LvcreateOptions "-m 1 /dev/nvme0n1 /dev/nvme1n1"
linstor sp sp px2 zfs_12_meta StorDriver/LvcreateOptions "-m 1 /dev/nvme0n1 /dev/nvme1n1"

I get this:

Description:
    (Node: 'px2') Failed to create lvm volume
Details:
    Command 'lvcreate --config devices { filter=['a|/dev/sdf3|','a|/dev/sdg3|','a|/dev/sdh3|','a|/dev/sdb3|','a|/dev/sdc3|','a|/dev/sdd3|','a|/dev/sde3|','a|/dev/nvme1n1|','a|/dev/nvme0n1|','a|/dev/sda3|','r|.*|'] } --size 7204k -n VG1/vm-107-disk-2.meta_00000 -y -m 1 /dev/nvme0n1 /dev/nvme1n1' returned with exitcode 3. 
    
    Standard out: 
    
    
    Error message: 
      Inconsistent volume group names given: "VG1" and "nvme0n1"
      Run `lvcreate --help' for more information.
    
    
    Node: px2, Storage pool name: zfs_12_meta
@ggzengel
Copy link
Author

For a work around I use this:

linstor sp sp px1 zfs_12_meta StorDriver/LvcreateOptions "-m 1 VG1 /dev/nvme0n1 /dev/nvme1n1"
SUCCESS:
    Successfully set property key(s): StorDriver/LvcreateOptions
SUCCESS:
Description:
    Storage pool 'zfs_12_meta' on node 'px1' modified.
Details:
    Storage pool 'zfs_12_meta' on node 'px1' UUID is: a1d8a9c1-7d16-4e0b-ba8d-6d093d0af959
SUCCESS:
    (px1) Changes applied to storage pool 'zfs_12_meta'
SUCCESS:
    (px1) Volume number 0 of resource 'vm-107-disk-2.meta' [LVM] created
SUCCESS:
    (px1) Resource 'vm-107-disk-2' [DRBD] adjusted.

@ghernadi
Copy link
Contributor

You are right. This will be fixed in the next release.

rp- pushed a commit that referenced this issue Sep 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants