Going from a 7.2.4 machine to a 7.3 machine. This is an update. Here's what the secondary says:
sim-array01*> snapvault status -l sim-array01:/vol/gso_shares/snapvault
Snapvault secondary is ON.
Source: 172.1.0.2:/vol/shares
Destination: sim-array01:/vol/gso_shares/snapvault
Status: Transferring
Progress: 1209016 KB
State: Snapvaulted
Lag: 39:53:10
Mirror Timestamp: Tue Dec 9 23:02:54 EST 2008
Base Snapshot: sim-array01(0101197614)_gso_shares-base.2
Current Transfer Type: Update
Current Transfer Error: -
Contents: Transitioning
Last Transfer Type: Update
Last Transfer Size: 19680896 KB
Last Transfer Duration: 05:11:29
Last Transfer From: 172.1.0.2:/vol/shares
And here is what's on the primary:
gvr-array02*> snapvault status -l sim-array01:/vol/gso_shares/snapvault
Snapvault primary is ON.
Source: gvr-array02:/vol/shares
Destination: sim-array01:/vol/gso_shares/snapvault
Status: Transferring
Progress: 1212912 KB
State: Source
Lag: 39:56:53
Mirror Timestamp: Tue Dec 9 23:02:54 EST 2008
Base Snapshot: sv_daily.1
Current Transfer Type: -
Current Transfer Error: -
Contents: -
Last Transfer Type: -
Last Transfer Size: 19680896 KB
Last Transfer Duration: 05:11:32
Last Transfer From: -
I am at a loss, do I need to kill it and do a -r? This is the second time it's stopped (last night it did the same thing and I had to kill it, thus the long Lag: time.
Please be advised that this email may contain confidential information. If you are not the intended recipient, please do not read, copy or re-transmit this email. If you have received this email in error, please notify us by email by replying to the sender and by telephone (call us collect at +1 202-828-0850) and delete this message and any attachments. Thank you in advance for your cooperation and assistance.
In addition, Danaher and its subsidiaries disclaim that the content of this email constitutes an offer to enter into, or the acceptance of, any contract or agreement or any amendment thereto; provided that the foregoing disclaimer does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment to this email.
Well actually eventually it continued. The extended status message added a line I've never seen before (not that I watch the transfers that closely since generally they seem to "just work".
It was updating Inodes. I assume since this is a relatively large (3.5 TB) volume with lots and lots of files that just takes a lot longer then on my other volumes. Just worried me a bit.
-----Original Message----- From: Chaim Rieger [mailto:lists@up-south.com] Sent: Thursday, December 11, 2008 3:31 PM To: Page, Jeremy Cc: toasters@mathworks.com Subject: Re: Snapvault hangs after tranfering a gig of data?
Page, Jeremy wrote:
I am at a loss, do I need to kill it and do a -r? This is the second time it's stopped (last night it did the same thing and I had to kill it, thus the long Lag: time.
snapvault snap list please on the source.
I've seen this with qtree snapmirror also - it appears to hang but it actually still transferring (you get the inode message) - typically in a filesystem with a large number of small files somewhere.
-----Original Message----- From: owner-toasters@mathworks.com on behalf of Page, Jeremy Sent: Thu 12/11/2008 12:32 PM To: Chaim Rieger Cc: toasters@mathworks.com Subject: RE: Snapvault hangs after tranfering a gig of data?
Well actually eventually it continued. The extended status message added a line I've never seen before (not that I watch the transfers that closely since generally they seem to "just work".
It was updating Inodes. I assume since this is a relatively large (3.5 TB) volume with lots and lots of files that just takes a lot longer then on my other volumes. Just worried me a bit.
-----Original Message----- From: Chaim Rieger [mailto:lists@up-south.com] Sent: Thursday, December 11, 2008 3:31 PM To: Page, Jeremy Cc: toasters@mathworks.com Subject: Re: Snapvault hangs after tranfering a gig of data?
Page, Jeremy wrote:
I am at a loss, do I need to kill it and do a -r? This is the second time it's stopped (last night it did the same thing and I had to kill it, thus the long Lag: time.
snapvault snap list please on the source.