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 1712315 - pcs config restore fails with Invalid cross-device link
Summary: pcs config restore fails with Invalid cross-device link
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.8
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1729984
TreeView+ depends on / blocked
 
Reported: 2019-05-21 10:27 UTC by Takayuki Nagata
Modified: 2020-03-31 19:10 UTC (History)
7 users (show)

Fixed In Version: pcs-0.9.168-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: /tmp is not located on the same disk partition as /etc Consequence: The 'pcs config restore' command fails with "unable to restore the cluster: [Errno 18] Invalid cross-device link" error. Fix: Move the files from backup to their desired locations using a function which can handle the files being on different partitions. Result: The 'pcs config restore' command works.
Clone Of:
Environment:
Last Closed: 2020-03-31 19:09:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (1.98 KB, patch)
2019-07-01 13:22 UTC, Tomas Jelinek 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3981151 0 Troubleshoot None Pacemaker cannot restore its configuration with Invalid cross-device link 2019-05-21 10:30:59 UTC
Red Hat Product Errata RHBA-2020:0996 0 None None None 2020-03-31 19:10:01 UTC

Comment 2 Tomas Jelinek 2019-07-01 13:22:01 UTC 
Created attachment 1586300 [details]
proposed fix

Test:

1) make sure /tmp is on a different disk partition than /etc (for example mount /tmp as tmpfs)
2) run `pcs config restore <backup file>`
Comment 4 Ivan Devat 2019-08-05 11:17:32 UTC 
After Fix:

[kid76 ~] $ rpm -q pcs
pcs-0.9.168-1.el7.x86_64

[kid76 ~] $ mount -t tmpfs -o size=25M tmpfs /tmp
[kid76 ~] $ pcs config backup test.backup
[kid76 ~] $ mv test.backup.tar.bz2 /tmp
[kid76 ~] $ pcs cluster stop --all
lion76: Stopping Cluster (pacemaker)...
kid76: Stopping Cluster (pacemaker)...
lion76: Stopping Cluster (corosync)...
kid76: Stopping Cluster (corosync)...
[kid76 ~] $ pcs config restore /tmp/test.backup.tar.bz2
kid76: Succeeded
lion76: Succeeded
Comment 8 errata-xmlrpc 2020-03-31 19:09:41 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-2020:0996
Note You need to log in before you can comment on or make changes to this bug.