Bug 586791
Summary: | Add support for persistent cache | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Rajnoha <prajnoha> |
Component: | lvm2 | Assignee: | Petr Rockai <prockai> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | agk, bmarzins, bmr, dwysocha, heinzm, jonathan, lvm-team, mclasen, msnitzer, prajnoha, prockai |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-18 14:21:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Peter Rajnoha
2010-04-28 11:46:57 UTC
(In reply to comment #0) > Excerpt from bug 570332: > - Make available vg_t, lv_t and pv_t objects based on _only_ what is > stored on the block device /dev/sdx Let's correct this one requirement... Considering the planned persistent cache, we won't provide information that is *only* stored on one exact block device, but we will provide the most recent information we will have in the cache. That means, including information about related VG even if that PV does not contain metadata, but we already have read metadata from another PV that references this PV. This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Persistent cache is provided by new "lvmetad" - the LVM metadata daemon which is upstream already, but it's still in active development (and not enabled in current Fedora yet). Let's keep this bz open to collect any related issues, problems and to track the progress. *** Bug 229560 has been marked as a duplicate of this bug. *** I guess we don't really need a tracker for this anymore. |