Bug 1729501
Summary: | Rear daily cron run fills temp directory upon failure | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Pavel Cahyna <pcahyna> |
Component: | rear | Assignee: | Pavel Cahyna <pcahyna> |
Status: | CLOSED ERRATA | QA Contact: | David Jež <djez> |
Severity: | high | Docs Contact: | Mariya Pershina <mpershin> |
Priority: | unspecified | ||
Version: | 8.0 | CC: | djez, lkuprova, ofalk, ovasik, pcahyna, peter.vreman, qe-baseos-apps |
Target Milestone: | rc | ||
Target Release: | 8.1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | rear-2.4-11.el8 | Doc Type: | Bug Fix |
Doc Text: |
.`ReaR` updates
RHEL 8.2 introduces a number of updates to the Relax-and-Recover (`ReaR`) utility.
The build directory handling has been changed. Previously, the build directory was kept in a temporary location in case `ReaR` encountered a failure. With this update, the build directory is deleted by default in non-interactive runs to prevent consuming disk space.
The semantics of the `KEEP_BUILD_DIR` configuration variable has been enhanced to include a new `errors` value. You can set the `KEEP_BUILD_DIR` variable to the following values:
* `errors` to preserve the build directory on errors for debugging (the previous behavior)
* `y` (`true`) to always preserve the build directory
* `n` (`false`) to never preserve the build directory
The default value is an empty string with the meaning of `errors` when `ReaR` is being executed interactively (in a terminal) and `false` if `ReaR` is being executed non-interactively. Note that `KEEP_BUILD_DIR` is automatically set to `true` in debug mode (`-d`) and in debugscript mode (`-D`); this behavior has not been changed.
Notable bug fixes include:
* Support for NetBackup 8.0 has been fixed.
* `ReaR` no longer aborts with a bash error similar to `xrealloc: cannot allocate` on systems with a large number of users, groups, and users per group.
* The `bconsole` command now shows its prompt, which enables you to perform a restore operation when using the Bacula integration.
* `ReaR` now correctly backs up files also in situations when the `docker` service is running but no `docker` root directory has been defined, or when it is impossible to determine the status of the `docker` service.
* Recovery no longer fails when using thin pools or recovering a system in Migration Mode.
* Extremely slow rebuild of `initramfs` during the recovery process with LVM has been fixed.
* `ReaR` now creates a working bootable ISO image on the AMD and Intel 64-bit architectures when using the UEFI bootloader. Booting a rescue image in this setup no longer aborts in Grub with the error message `Unknown command 'configfile' (...) Entering rescue mode...`. Support for GRUB_RESCUE in this setup, which previously could fail due to missing XFS filesystem support, has also been fixed.
|
Story Points: | --- |
Clone Of: | 1693608 | Environment: | |
Last Closed: | 2020-04-28 15:47:07 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1693608 | ||
Bug Blocks: |
Comment 6
errata-xmlrpc
2020-04-28 15:47:07 UTC
|