Project

General

Profile

Actions
Copy link

Bug #37411

closed

zapping a device not that is a pv but with no vgs fails

Added by Andrew Schoen over 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When running `ceph-volume lvm zap --destroy` against a device that is a pv but has not been used for a vg fails.

[root@osd0 vagrant]# pvs
  PV           VG         Fmt  Attr PSize   PFree
  /dev/nvme1n1            lvm2 ---   10.00g 10.00g
  /dev/sda3    VolGroup00 lvm2 a--  <38.97g     0
[root@osd0 vagrant]# vgs
  VG         #PV #LV #SN Attr   VSize   VFree
  VolGroup00   1   2   0 wz--n- <38.97g    0
[root@osd0 vagrant]# ceph-volume lvm zap --destroy /dev/nvme1n1
Running command: /usr/sbin/cryptsetup status /dev/mapper/
--> Zapping: /dev/nvme1n1
--> Destroying volume group  because --destroy was given
Running command: /usr/sbin/vgremove -v -f
 stderr: VG name on command line not found in list of VGs:
  Volume group name "" has invalid characters.
  Cannot process volume group
--> Unable to remove vg
-->  RuntimeError: command returned non-zero exit status: 5
Actions
Copy link
 #1

Updated by Alfredo Deza almost 5 years ago

  • Status changed from New to Resolved

This is no longer an issue:

[root@node3 vagrant]# pvcreate /dev/sdac
  Physical volume "/dev/sdac" successfully created.
[root@node3 vagrant]# ceph-volume lvm zap --destroy /dev/sdac
--> Zapping: /dev/sdac
Running command: /usr/sbin/wipefs --all /dev/sdac
 stdout: /dev/sdac: 8 bytes were erased at offset 0x00000218 (LVM2_member): 4c 56 4d 32 20 30 30 31
Running command: /bin/dd if=/dev/zero of=/dev/sdac bs=1M count=10
 stderr: 10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.00336308 s, 3.1 GB/s
--> Zapping successful for: <Raw Device: /dev/sdac>
Actions
Copy link

Also available in: Atom PDF