Okay, but how/where/what to check exactly? And is the lack of recent entries in the source system rsync.log expected?
Type: Posts; User: rmoulton
Okay, but how/where/what to check exactly? And is the lack of recent entries in the source system rsync.log expected?
Strange. On the source system 'gverc', the timestamp on rsync.log is 2014-07-29 16:18. I don't see anything logged since then.
On the destination system 'dunkel', the rsync.log is full of entries...
Two identical DSS 6 systems here, version 6.0up98.8101.7337 64bit (updates u01384, u01236).
A daily replication task between the two systems keeps reporting errors like this (a couple of times a...
the small update has been re-applied, and the FSIDs are now present/displayed again, but I still get the error. What next?
today I updated the system to ...
6.0up98.8101.7337 64bit
... and did a filesystem repair. Unfortunately the "no space" behavior persists. I notice that the NFS option to specify the FSID has...
after successfully applying the update and setting FSIDs for the two shares on the system (FSID 1 and FSID 2, respectively), I remounted the share in question and found that I still get the "No space...
that's what I assumed, but I can't locate such a box. Would it only be available/visible after the update is applied?
okay, thanks. That sounds fairly straightforward, with the exception of setting the FSID. Where/how is that done?
thanks for the replies, but now I'm confused about how to proceed. Should I submit a support ticket or apply the update? If the latter, how do I apply the update, exactly, and is there any danger of...
Two identical DSS 6 systems here:
Model: Data Storage Software V6
Version: 6.0up97.8101.6325 64bit
Release date: 2012-06-15
Licensed Storage Capacity: unlimited
The first system provides...