Bug 1269793 - RFE: Add support for printing content of ring-buffer
RFE: Add support for printing content of ring-buffer
Status: NEW
Product: Fedora
Classification: Fedora
Component: lvm2 (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: LVM and device-mapper development team
Fedora Extras Quality Assurance
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2015-10-08 04:53 EDT by Zdenek Kabelac
Modified: 2015-10-08 06:41 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Zdenek Kabelac 2015-10-08 04:53:26 EDT
Description of problem:

There is no 'easy' way to readout content of ring-buffer
e.g. when user is in dracut - there is no 'dd' command,
and retrieving content of previous metadata for being able to run 'vgcfgrestore' is getting tricky if the root volume with archive is unavailable.

So IMHO easiest would be to extent some lvm2 command to be able to dump content of present metadata in the ring-buffer into a file.

i.e.  --scanbufffer {all|#number}  to read last #number of entries and store them into a file - when a PV is given - list just metadata from this PV, otherwise scan and check all devices for metadata

Something in this direction would be quite useful.

It could be possible paired with 'vgcfgrestore --list' 
as i.e.  'vgcfgrestore --scandisk'

so it may eventually work directly without need of temporary file storage -
i.e. revert back by 'x' metadata from given time as listed....

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

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