-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thin pool recreation logic / use of vgcfgrestore is broken #2222
Comments
What properties would be lost? To preserve segment properties, I proposed using lvextend for each segment separately, see https://bugzilla.redhat.com/show_bug.cgi?id=1732328#c21 |
Tons of properties, and also dependent on the release of LVM2. |
@dwlehman, do you please have any advice on how to save LVM configuration for later recreation on a different system, while preserving the above mentioned properties and not relying on vgcfgrestore? |
A general note one such kind of issues: There are many other cases where ReaR does not support E.g. arbitrary file system tuning parameters are often not supported Currently in very most cases "rear mkrescue" does not even detect Currently this is how ReaR is meant to be used: So - from my point of view - what would help first and foremost is Such cases (missing functionality in ReaR) would be neither an |
I missed that in current ReaR the bug is that vgcfgrestore is the wrong tool |
So, the strategy could be:
By the way, I looked at what Clonezilla is doing. From a quick look at the sources, they seem to restore using vgcfgrestore, and don't mention anything special for thin pools at all, so they probablty have not considered this use case either. |
A side note FYI |
In general regarding "warn the user" see That's why I would prefer to error out with something like a
plus - to "provide final power to the user" - a new config variable |
@jsmeix I meant to "warn the user" by erroring out actually, I agree that just log a warning and continue is not that helpful. The key part though is to detect the problem during the mkrescue step, not during the recovery step, when it is too late. |
…is broken Removing forcibly (with '--force' passed twice) just works. Signed-off-by: Renaud Métrich <rmetrich@redhat.com>
Fix for #2222 - Thin pool recreation logic / use of vgcfgrestore is broken
Stale issue message |
so, is unclear to me what the status closed of this issue means: is ReaR able or not to recreate a lvm on thin pool structure like this?
it's created by rhel8 gui installer |
rhel bugzilla 1747468 has no comments since 2019 while only in summer 2020 went into assigned status and in april this year went into high priority |
@mailinglists35 Please ask assistance via BZ for that particular case. |
@gdha hello, yes, it is on my ToDo list. |
@pcahyna |
Stale issue message |
I think the bot has closed the issue prematurely. ReaR still cannot recreate a thin pool structure. If you don't want / have no resources to support this, perhaps you should mention it. also related upstream BZ is still open |
@mailinglists35 @rmetrich @pcahyna On request we re-open this issue. |
hello @mailinglists35 , I have a patch that improves the situation and I will open a PR. Do you have a test case that you can try? |
Thank you! see an example in my older comment: #2222 (comment)
…
On Sep 14, 2021 at 8:40 PM, <pcahyna ***@***.***)> wrote:
hello @mailinglists35 (https://github.com/mailinglists35) , I have a patch that improves the situation and I will open a PR. Do you have a test case that you can try?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (#2222 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAPVRHTQI6PQQ3P6TRFPOBDUB6CI5ANCNFSM4IS5PIOA).
|
Hello @mailinglists35, if you have a system on which you can test, please try my branch https://github.com/pcahyna/rear/tree/thinpools-layout. |
By the way, what version of ReaR have you tried and what errors did you get on your thin pool layout? |
Hello @mailinglists35, I am still interested what errors did you get and if my branch improves the situation. |
I'm sorry I wasn't able to try your patched version until now, will take a couple of weeks more until I can get around that machine |
Stale issue message |
oh I forgot to try your branch |
@mailinglists35 any updates? |
Stale issue message |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"): ** ALL, including latest**
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"): All Linux using LVM2
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR): ALL
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device): ALL
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot): ALL
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe): ALL
Description of the issue (ideally so that others can reproduce it):
With #1806 we fixed LVM2 volume group recreation when volume groups had Thin pools.
The idea consisted in using
vgcfgrestore
then deleting the Thin pools and recreating them usinglvcreate
commands.It appears that this is not working properly, see Red Hat BZ https://bugzilla.redhat.com/show_bug.cgi?id=1747468 for details.
Additionally, our use of
vgcfgrestore
is probably not appropriate at all, it works by chance (see comment https://bugzilla.redhat.com/show_bug.cgi?id=1747468#c3 for details). Typically, it works only for Linear volumes, and won't probably for Caches and Raid hierarchies or when there are existing Snapshots on the system.The only proper solution I see is stop relying on
vgcfgrestore
at all, but then we are not capable of restoring volume groups and logical volumes with all properties from original system.So what should we do now???
The text was updated successfully, but these errors were encountered: