Red Hat Bugzilla – Bug 903587
lvmdump does not handle symbolic links nor modified backup.backup_dir or backup.archive_dir
Last modified: 2014-01-19 22:02:58 EST
lvmdump does not handle symbolic links nor modified backup_dir or archive_dir.
This makes sense on systems with read-only /etc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create /etc/lvm as a symbolic link
2. modify lvm.conf so backup_dir/archive_dir points to non-default location
3. run lvmdump -ma
- link is archived not the content
- backup/archive dir are not archived
- content of /etc/lvm/ should be archived
- backup/archive dir should be archived
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Symbolic links are now followed + a directory listing is included (just for sure to see which files/dirs were symlinks originally):
lvm2-2.02.98-14.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lvm2-2.02.98-14.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
lvm2-2.02.98-14.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.