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.
Bug 1084081 - device-mapper-persistent-data: add critical needs_check flag and new era tools [technology preview]
Summary: device-mapper-persistent-data: add critical needs_check flag and new era tool...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: device-mapper-persistent-data
Version: 6.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 6.6
Assignee: Heinz Mauelshagen
QA Contact: yanfu,wang
URL:
Whiteboard:
Depends On:
Blocks: 1086824
TreeView+ depends on / blocked
 
Reported: 2014-04-03 14:51 UTC by Heinz Mauelshagen
Modified: 2021-04-29 14:53 UTC (History)
17 users (show)

Fixed In Version: device-mapper-persistent-data-0.3.2-1.el6
Doc Type: Technology Preview
Doc Text:
⁠dm-era Technology Preview The device-mapper-persistent-data package now provides tools to help use the new dm-era device mapper functionality released as a Technology Preview. The dm-era functionality keeps track of which blocks on a device were written within a user-defined period of time called an era. This functionality allows backup software to track changed blocks or restore the coherency of a cache after reverting changes.
Clone Of: 1081546
Environment:
Last Closed: 2014-10-14 04:36:00 UTC
Target Upstream Version:
Embargoed:
heinzm: needinfo-
heinzm: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1409 0 normal SHIPPED_LIVE device-mapper-persistent-data bug fix and enhancement update 2014-10-14 00:54:53 UTC

Description Heinz Mauelshagen 2014-04-03 14:51:39 UTC
Description of problem:
device-mapper-persistent-data needs new userspace tools to support
the new dm-era target supporting dm-cache coherency with storage
subsystem snapshots. E.g. to invalidate a certain era refering to
a hardware snapshot.

Version-Release number of selected component (if applicable):


How reproducible:
if using the dm-era target, no tools exist to e.g. invalidate any
eras or check the era metadata.

Steps to Reproduce:
1. setup dm-era mapping
2.
3.

Actual results:
Mapping created but no tools to actually set eras.

Expected results:
Tools available to set eras

Additional info:

Comment 1 Heinz Mauelshagen 2014-04-09 09:11:17 UTC
Package built.

Comment 15 errata-xmlrpc 2014-10-14 04:36:00 UTC
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.

http://rhn.redhat.com/errata/RHBA-2014-1409.html


Note You need to log in before you can comment on or make changes to this bug.