Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I use netapp's XCP at our data migration project .
"xcp copy" was succed ,and "xcp sync" was suceed too.
But some error occured when "xcp sync" was done in a week .
Following error is written in a xcp.log .
xcp 2017-12-06 16:01:48 rescan 'Server:/cfs046a/xxx' ERROR: rescan 'Server:/cfs046a/xxx': 'rd.Dir3' object has no attribute 'parfh'
xcp 2017-12-06 16:01:48 rescan 'Server:/cfs046a/xxx' ERROR: Traceback (most recent call last):
File "sched.pyx", line 579, in sched.Engine._runTasks (sched.c:14759)
File "sched.pyx", line 1567, in sched.Task.run (sched.c:39275)
File "../sync.py", line 1568, in gWhatsNew
File "../idx.py", line 915, in getTargetPath
File "../idx.py", line 885, in __init__
AttributeError: 'rd.Dir3' object has no attribute 'parfh'
What has happened?
This server has a lot of update data , Is that safe to retry " xcp sync" ?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you doing sync when data was changin on source ?
![](/skins/images/F656501F534EE6F07310F744781865A1/responsive_peak/images/icon_anonymous_message.png)