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 1631183 - Backup using tar always succeeds, even in case of tar error
Summary: Backup using tar always succeeds, even in case of tar error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rear
Version: 7.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
URL:
Whiteboard:
Depends On:
Blocks: 1594286 1630904 1630910 1630919 1657734 1660473
TreeView+ depends on / blocked
 
Reported: 2018-09-20 07:39 UTC by Renaud Métrich
Modified: 2021-12-10 17:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1657734 (view as bug list)
Environment:
Last Closed: 2019-08-06 13:12:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear rear issues 1913 0 None closed NETFS+tar backup tests wrong exit code (may succeed even if there was a real error) 2020-03-16 02:39:45 UTC
Github rear rear pull 1914 0 None closed Issue #1913 - NETFS+tar backup exit code testing insufficient (may fail to catch real backup errors) 2020-03-16 02:39:46 UTC
Red Hat Knowledge Base (Solution) 3618561 0 None None None 2018-09-20 08:47:23 UTC
Red Hat Product Errata RHBA-2019:2273 0 None None None 2019-08-06 13:12:31 UTC

Description Renaud Métrich 2018-09-20 07:39:57 UTC 
Description of problem:

It appears that the ReaR backup code using "tar" is broken and indicates always a success even in case "tar" returned an error.


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

rear-2.00-7.el7_5.x86_64


How reproducible:

Always


Steps to Reproduce:
1. Configure rear to backup to a location which is too small to contain the backup (e.g. leave 300M free on a LV)

# cat /etc/rear/site.conf 
OUTPUT=ISO
OUTPUT_URL=file:///backup
BACKUP=NETFS
BACKUP_URL=file:///backup
ONLY_INCLUDE_VG=( 'rhel' )

# mount /dev/data/lv /backup
# dd if=/dev/zero of=/backup/bigfile bs=1M count=700

2. Run the backup

# rear -v mkbackuponly


Actual results:

WARNING: tar ended with return code 1 and below output:
  ---snip---

  ----------
This means that files have been modified during the archiving
process. As a result the backup may not be completely consistent
or may not be a perfect copy of the system. Relax-and-Recover
will continue, however it is highly advisable to verify the
backup in order to be sure to safely recover this system.

Archived 762 MiB in 88 seconds [avg 8874 KiB/sec]


Expected results:

The real error (there is no issue with "tar", but "dd" returned 1 because ENOSPACE)


Additional info:

Issue happens with Upstream ReaR also.
Comment 19 errata-xmlrpc 2019-08-06 13:12:05 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.

https://access.redhat.com/errata/RHBA-2019:2273
Note You need to log in before you can comment on or make changes to this bug.