Skip to navigation

Bug Fix Advisory dump bug fix update

Advisory: RHBA-2010:0591-2
Type: Bug Fix Advisory
Severity: N/A
Issued on: 2011-02-16
Last updated on: 2011-02-16
Affected Products: Red Hat Desktop (v. 4)
Red Hat Enterprise Linux AS (v. 4)
Red Hat Enterprise Linux ES (v. 4)
Red Hat Enterprise Linux WS (v. 4)

Details

Updated dump packages that resolve several issues are now available.

The dump package contains both dump and restore commands. The dump command
examines files in a file system, determines which ones need to be backed
up, and copies those files to a specified disk, tape, or other storage
medium. The restore command performs the inverse function of dump; it can
restore a full backup of a file system. Subsequent incremental backups can
then be layered on top of the full backup. Single files and directory
subtrees may also be restored from full or partial backups.

These updated dump packages addresses the following issues:

* two bugs, one in a restore command reference and one in removeoldnodes()
function logic, were found. In some circumstances these bugs meant that, if
a level 1 dump (ie an incremental back up) was performed after a level 0
dump (ie a backup of a complete file system) and restoration of the level 1
dump was then attempted, the restoration would fail with a segmentation
fault. With this update the restore command reference and the function
logic were both corrected and restoration of incremental backups in such
circumstances works as expected. (BZ#557026)

* the "-N" switch, which sets the restore utility to to run a restoration
without actually writing files to disk (ie a "dry run") was not properly
ignored by the xattr_cb_set() function (this function sets extended
attributes or xattributes). Consequently, in some circumstances, when
"restore -N" was run it still attempted to write xattributes to disk. This
resulted in errors such as follows:

restore: lsetxattr /path/to/file failed: No such file or directory

With this update, the "-N" option is properly recognized by xattr_cb_set()
and no attempt to write xattributes occurs when the "-N" switch is used.
(BZ#568457)

* errors in calculating offsets from which to continue file restoration
meant that, if a file was split across multiple tapes during a backup, the
split file was corrupted and presented with a different md5sum hash to the
original when restoration was attempted. This update corrects the offset
calculations and allows restoration of split files as expected. (BZ#507948)

All dump users should upgrade to these updated packages, which resolve
these issues.


Solution

Before applying this update, make sure all previously-released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/docs/DOC-11259

Updated packages

Red Hat Desktop (v. 4)

SRPMS:
dump-0.4b39-5.el4.src.rpm     MD5: a57813a37cb21cb19bbaaef966b37c7d
SHA-256: 771286dd5a86b47c9f9fa507f4861e73553b8f5c3ab89961947ae572917a4365
 
IA-32:
dump-0.4b39-5.el4.i386.rpm     MD5: 3208a1d969b03855dc30c9f4c9247d91
SHA-256: 56300dd57b060f2c275afc464ad49a0ac2c165a981d65e29ef860db1368e41af
rmt-0.4b39-5.el4.i386.rpm     MD5: d1763710c88f24421a4901f7bbc9524f
SHA-256: 93dcc8fb9666381f0d2f8b4c1a060530b506892037b4cba84852a8e35b70948a
 
x86_64:
dump-0.4b39-5.el4.x86_64.rpm     MD5: 58612bfc6f4668875c171dc96e040013
SHA-256: 4433c474ce5c21f41964a2daba2de2388d03d519af2be2d0ee2ff6e45f4d3363
rmt-0.4b39-5.el4.x86_64.rpm     MD5: 74407bd5c6fa851ae89e042cd8b47f20
SHA-256: fec944e7da9a87dc0b31f9dbd374dd921490b16435757c3c0378eb02ca41309e
 
Red Hat Enterprise Linux AS (v. 4)

SRPMS:
dump-0.4b39-5.el4.src.rpm     MD5: a57813a37cb21cb19bbaaef966b37c7d
SHA-256: 771286dd5a86b47c9f9fa507f4861e73553b8f5c3ab89961947ae572917a4365
 
IA-32:
dump-0.4b39-5.el4.i386.rpm     MD5: 3208a1d969b03855dc30c9f4c9247d91
SHA-256: 56300dd57b060f2c275afc464ad49a0ac2c165a981d65e29ef860db1368e41af
rmt-0.4b39-5.el4.i386.rpm     MD5: d1763710c88f24421a4901f7bbc9524f
SHA-256: 93dcc8fb9666381f0d2f8b4c1a060530b506892037b4cba84852a8e35b70948a
 
IA-64:
dump-0.4b39-5.el4.ia64.rpm     MD5: 49e5afbd0c4f93f44a9a34390e0bdaff
SHA-256: 2b9d8914adc15ead4289b324767a49062c2fcee81ce7cd3b0baa0934349f8579
rmt-0.4b39-5.el4.ia64.rpm     MD5: cbb1c89d01d143fa64c02bdd5d3a34c2
SHA-256: 1871ee31c557e3147da078ec53fcc6e003446af29517fe83bc42f6a8c5295975
 
PPC:
dump-0.4b39-5.el4.ppc.rpm     MD5: 5f9a9ecb89f3ee7b5d9ef14109274084
SHA-256: 2e9eb3597f8d29a354f93b9ee638a7437a479b95eeefd02c2344054225ffca0e
rmt-0.4b39-5.el4.ppc.rpm     MD5: 7f2af91a860bd46b85f0090e8c7b9fb0
SHA-256: 7c32cf7db1cb7cefaf8559e3bdd99ba36c6e9d5271107bf5a1b1027639e4b203
 
s390:
dump-0.4b39-5.el4.s390.rpm     MD5: 51666c9cb9fdbfe84f516f8763c3fac8
SHA-256: 54fb20376822a7d0cb6447f401df5e869d58012d50cc5a9979560d9cde7a97d2
rmt-0.4b39-5.el4.s390.rpm     MD5: f86444bdb10c9fffcb510aebf1045066
SHA-256: a75de99246521ee7a1ad88f9290a729769b2d0e2cb7f9b1e21d90f71332fe836
 
s390x:
dump-0.4b39-5.el4.s390x.rpm     MD5: 46e9f98b5752d42e0fd273051a333458
SHA-256: 392cb76a527a7d1751a21857f02fdfa139ace6c7354b77cd191bbee8d81ec20f
rmt-0.4b39-5.el4.s390x.rpm     MD5: 14276fcca437bf8fa71a097f38cbfefb
SHA-256: 383aee268897098f85dd679aff626d7fecb8c8c08d8c54ecf8bb39cf01087a57
 
x86_64:
dump-0.4b39-5.el4.x86_64.rpm     MD5: 58612bfc6f4668875c171dc96e040013
SHA-256: 4433c474ce5c21f41964a2daba2de2388d03d519af2be2d0ee2ff6e45f4d3363
rmt-0.4b39-5.el4.x86_64.rpm     MD5: 74407bd5c6fa851ae89e042cd8b47f20
SHA-256: fec944e7da9a87dc0b31f9dbd374dd921490b16435757c3c0378eb02ca41309e
 
Red Hat Enterprise Linux ES (v. 4)

SRPMS:
dump-0.4b39-5.el4.src.rpm     MD5: a57813a37cb21cb19bbaaef966b37c7d
SHA-256: 771286dd5a86b47c9f9fa507f4861e73553b8f5c3ab89961947ae572917a4365
 
IA-32:
dump-0.4b39-5.el4.i386.rpm     MD5: 3208a1d969b03855dc30c9f4c9247d91
SHA-256: 56300dd57b060f2c275afc464ad49a0ac2c165a981d65e29ef860db1368e41af
rmt-0.4b39-5.el4.i386.rpm     MD5: d1763710c88f24421a4901f7bbc9524f
SHA-256: 93dcc8fb9666381f0d2f8b4c1a060530b506892037b4cba84852a8e35b70948a
 
IA-64:
dump-0.4b39-5.el4.ia64.rpm     MD5: 49e5afbd0c4f93f44a9a34390e0bdaff
SHA-256: 2b9d8914adc15ead4289b324767a49062c2fcee81ce7cd3b0baa0934349f8579
rmt-0.4b39-5.el4.ia64.rpm     MD5: cbb1c89d01d143fa64c02bdd5d3a34c2
SHA-256: 1871ee31c557e3147da078ec53fcc6e003446af29517fe83bc42f6a8c5295975
 
x86_64:
dump-0.4b39-5.el4.x86_64.rpm     MD5: 58612bfc6f4668875c171dc96e040013
SHA-256: 4433c474ce5c21f41964a2daba2de2388d03d519af2be2d0ee2ff6e45f4d3363
rmt-0.4b39-5.el4.x86_64.rpm     MD5: 74407bd5c6fa851ae89e042cd8b47f20
SHA-256: fec944e7da9a87dc0b31f9dbd374dd921490b16435757c3c0378eb02ca41309e
 
Red Hat Enterprise Linux WS (v. 4)

SRPMS:
dump-0.4b39-5.el4.src.rpm     MD5: a57813a37cb21cb19bbaaef966b37c7d
SHA-256: 771286dd5a86b47c9f9fa507f4861e73553b8f5c3ab89961947ae572917a4365
 
IA-32:
dump-0.4b39-5.el4.i386.rpm     MD5: 3208a1d969b03855dc30c9f4c9247d91
SHA-256: 56300dd57b060f2c275afc464ad49a0ac2c165a981d65e29ef860db1368e41af
rmt-0.4b39-5.el4.i386.rpm     MD5: d1763710c88f24421a4901f7bbc9524f
SHA-256: 93dcc8fb9666381f0d2f8b4c1a060530b506892037b4cba84852a8e35b70948a
 
IA-64:
dump-0.4b39-5.el4.ia64.rpm     MD5: 49e5afbd0c4f93f44a9a34390e0bdaff
SHA-256: 2b9d8914adc15ead4289b324767a49062c2fcee81ce7cd3b0baa0934349f8579
rmt-0.4b39-5.el4.ia64.rpm     MD5: cbb1c89d01d143fa64c02bdd5d3a34c2
SHA-256: 1871ee31c557e3147da078ec53fcc6e003446af29517fe83bc42f6a8c5295975
 
x86_64:
dump-0.4b39-5.el4.x86_64.rpm     MD5: 58612bfc6f4668875c171dc96e040013
SHA-256: 4433c474ce5c21f41964a2daba2de2388d03d519af2be2d0ee2ff6e45f4d3363
rmt-0.4b39-5.el4.x86_64.rpm     MD5: 74407bd5c6fa851ae89e042cd8b47f20
SHA-256: fec944e7da9a87dc0b31f9dbd374dd921490b16435757c3c0378eb02ca41309e
 
(The unlinked packages above are only available from the Red Hat Network)

Bugs fixed (see bugzilla for more information)

557026 - Segmentation fault occurs when a customer restores data were taken by incremental backup
568457 - restore -rN attempts to lsetxattr files not restored


Keywords

incremental, lsetxattr, restore


These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/