Hello,
'vos move' of a big volume (8.7TB) id 537070263 failed with reporting
the following messages in VolserLog on the target server:
###
Tue May 30 11:41:49 2017 1 Volser: WriteFile: Error reading dump file
171404 size=240744204 nbytes=215734028 (0 of 8192): File exists; restore
aborted
Tue May 30 11:41:49 2017 1 Volser: ReadVnodes: IDEC inode 459308097772940
Tue May 30 11:43:55 2017 Scheduling salvage for volume 537070263 on part
/vicepb over FSSYNC
Tue May 30 11:43:55 2017 SYNC_ask: negative response on circuit 'FSSYNC'
Tue May 30 11:43:55 2017 FSYNC_askfs: FSSYNC request denied for reason=65537
Tue May 30 11:43:55 2017 VAttachVolume: file server says volume
537070263 is salvaging
Tue May 30 11:43:55 2017 Scheduling salvage for volume 537070263 on part
/vicepb over FSSYNC
Tue May 30 11:43:58 2017 SYNC_ask: negative response on circuit 'FSSYNC'
Tue May 30 11:43:58 2017 FSYNC_askfs: FSSYNC request denied for reason=65537
Tue May 30 11:43:58 2017 VAttachVolume: file server says volume
537070263 is salvaging
Tue May 30 11:43:58 2017 Scheduling salvage for volume 537070263 on part
/vicepb over FSSYNC
Tue May 30 11:44:01 2017 SYNC_ask: negative response on circuit 'FSSYNC'
Tue May 30 11:44:01 2017 FSYNC_askfs: FSSYNC request denied for reason=65537
Tue May 30 11:44:01 2017 VAttachVolume: file server says volume
537070263 is salvaging
Tue May 30 11:44:01 2017 Scheduling salvage for volume 537070263 on part
/vicepb over FSSYNC
Tue May 30 11:44:36 2017 1 Volser: Delete: volume 537070263 deleted
###
'bos salvage' was run for the volume befor, but reported no problems.
OpenAFS version is 1.6.20.2 .
What could be the reason for such kind of problem and how it can be fixed?
Thanks,
Andreas
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
