Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After creating a VDO device on a block device, that block device should get some udev properties that labels it as a "vdo backing device" or similar, just LVM2 like physical volumes.
Version-Release number of selected component (if applicable):
vdo-6.1.0.0-6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. vdo create --name vdo0 --device /dev/sda
2. vdo stop --name vdo0
2. blkid -p /dev/sda
3. wipefs -n /dev/sda
Actual results:
# blkid -p /dev/sda
<empty>
# wipefs -n /dev/sda
<empty>
Expected results:
Not sure, tbh. blkid should show at least something for TYPE and USAGE, and wipefs should recognize the signature and be able to erase it.
Additional info:
For LVM2 physical volumes, the output is like this:
# pvcreate /dev/sda
# blkid -p /dev/sda
/dev/sda: UUID="uVdwaj-l03E-Nktv-aKzS-DAf6-6qhk-W3fG4r" VERSION="LVM2 001" TYPE="LVM2_member" USAGE="raid"
# wipefs -n /dev/sda
offset type
----------------------------------------------------------------
0x218 LVM2_member [raid]
UUID: uVdwaj-l03E-Nktv-aKzS-DAf6-6qhk-W3fG4r
There is an RFE for this feature https://bugzilla.redhat.com/show_bug.cgi?id=1509336, which is expected to be supported in RHEL 7.6 and 8.0.
Since this will not be supported in 7.5 we should consider closing this ticket.
Is there any requirement from cockpit that requires this feature or is it a nice
to have?
(In reply to Dennis Keefe from comment #2)
> Is there any requirement from cockpit that requires this feature or is it a
> nice to have?
It is "nice to have". I wasn't aware of the RFE, and this report here is a duplicate of the RFE.
I cannot see any change based on reproducer specified in this BZ:
# vdo create --name vdo --device /dev/sdc
Creating VDO vdo
vdo stop --name vdo
blStarting VDO vdo
kStarting compression on VDO vdo
iVDO instance 7 volume is ready at /dev/mapper/vdo
# vdo stop --name vdo
Stopping VDO vdo
# blkid -p /dev/sdc
# wipefs -n /dev/sdc
Both blkid and wipefs are still empty, what is the change here?
Yesterday, new version ov blkid was built that supports vdo identification. These are the versions I used to test this:
kmod-kvdo-6.1.0.98-11.el7.x86_64.rpm
libblkid-2.23.2-49.el7.x86_64.rpm
libmount-2.23.2-49.el7.x86_64.rpm
libuuid-2.23.2-49.el7.x86_64.rpm
util-linux-2.23.2-49.el7.x86_64.rpm
uuidd-2.23.2-49.el7.x86_64.rpm
vdo-6.1.0.98-13.x86_64.rpm
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
--snip--
sdc 8:32 0 5.5T 0 disk
└─vdo 253:2 0 5.5T 0 vdo
# blkid -p /dev/sdc
/dev/sdc: UUID="fee52367-c2ca-4fab-a6e9-58267895fe3f" TYPE="vdo" USAGE="other"
# wipefs -n /dev/sdc
offset type
----------------------------------------------------------------
0x0 vdo [other]
UUID: fee52367-c2ca-4fab-a6e9-58267895fe3f
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2018:0871
Description of problem: After creating a VDO device on a block device, that block device should get some udev properties that labels it as a "vdo backing device" or similar, just LVM2 like physical volumes. Version-Release number of selected component (if applicable): vdo-6.1.0.0-6.x86_64 How reproducible: Always Steps to Reproduce: 1. vdo create --name vdo0 --device /dev/sda 2. vdo stop --name vdo0 2. blkid -p /dev/sda 3. wipefs -n /dev/sda Actual results: # blkid -p /dev/sda <empty> # wipefs -n /dev/sda <empty> Expected results: Not sure, tbh. blkid should show at least something for TYPE and USAGE, and wipefs should recognize the signature and be able to erase it. Additional info: For LVM2 physical volumes, the output is like this: # pvcreate /dev/sda # blkid -p /dev/sda /dev/sda: UUID="uVdwaj-l03E-Nktv-aKzS-DAf6-6qhk-W3fG4r" VERSION="LVM2 001" TYPE="LVM2_member" USAGE="raid" # wipefs -n /dev/sda offset type ---------------------------------------------------------------- 0x218 LVM2_member [raid] UUID: uVdwaj-l03E-Nktv-aKzS-DAf6-6qhk-W3fG4r