[OpenAFS] same-server partition moves?

2015-12-09 Thread Jeff Blaine 
If you had to bulk migrate online volumes across partitions on the same
server, would you just stick to 'vos move'? Other options?
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Odd error on 'vos move'

2015-12-09 Thread Garance A Drosehn 
On 7 Dec 2015, at 15:51, Benjamin Kaduk wrote:

> On Mon, 7 Dec 2015, Garance A Drosehn wrote:
>
>> Hi.
>>
>> I've been busy moving our AFS volumes from ancient file servers to
>> up-to-date file servers.  So far this has been going along well,
>> but last week I ran into an odd error moving one 10.79 GiB file.
>>
>> My main question is:  Could a problem like this be caused by my
>> AFS token expiring in the middle of the transfer?  [...]
>
> That sounds like a correct procedure.  Note that the credentials
> used by -localauth do not expire; I suggest using that for a
> long-running move.

Ooo.  That's a good idea, and kind of obvious now that you've pointed
it out.  Much better than having my script parse the output of the
'tokens' command to see how much time is left!  Thanks!

-- 
Garance Alistair Drosehn= dro...@rpi.edu
Senior Systems Programmer   or   g...@freebsd.org
Rensselaer Polytechnic Institute; Troy, NY;  USA
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: [OpenAFS] Odd error on 'vos move'

2015-12-09 Thread Garance A Drosehn 

On 7 Dec 2015, at 15:52, Brandon Allbery wrote:

That looks like pretty much textbook token expiration in mid-volume 
copy, yes. You will need to "vos unlock" the original volume and 
possibly "vos endtrans" on the server (warning, this ends *all* active 
transactions! Might be better to wait 10-15 minutes for it to time 
out).


It shouldn't be necessary to do anything about the destination unless 
you decided not to do the move after all; it should reuse the 
incomplete volume.


My original idea was to vos-remove the incomplete copy from the 
destination *before* unlocking the volume, but AFS didn't like that 
idea.


So I vos-unlocked the volume, waited a little while (just because 
something else interrupted me at work), and then redid the vos-move 
command.  I did not try to delete the off-line copy of the volume which 
was sitting on the destination before doing the vos-move.  Everything 
seems to have worked fine.  Thanks!


FWIW, this is how the operation looked:

 time /usr/sbin/vos move -id <_details_>  -verbose -localauth
  Starting transaction on source volume <__old__> ... done
  Allocating new volume id for clone of volume <__old__> ... done
  Cloning source volume <__old__> ... done
  Ending the transaction on the source volume <__old__> ... done
  Starting transaction on the cloned volume <_clone_> ... done
  Setting flags on cloned volume <_clone_> ... done
  Getting status of cloned volume <_clone_> ... done
  Deleting pre-existing destination volume <__old__> ... done
  Creating the destination volume <__old__> ... done
  Setting volume flags on destination volume <__old__> ... done
  Dumping from clone <_clone_> on source to volume <__old__> on 
destination ... done

  Ending transaction on cloned volume <_clone_> ... done
  Starting transaction on source volume <__old__> ... done
  Doing the incremental dump from source to destination for volume 
<__old__> ...  done

  Setting volume flags on old source volume <__old__> ... done
  Setting volume flags on new source volume <__old__> ... done
  Ending transaction on destination volume <__old__> ... done
  Releasing lock on VLDB entry for volume <__old__> ... done
  Setting forwarding pointer for volume <__old__> ... done
  Deleting old volume <__old__> on source ... done
  Ending transaction on old volume <__old__> on the source ... done
  Deleting source backup volume <_oldBK_> ... done
  Deleting cloned volume <_clone_> ... done
  Volume <__old__> moved from  to 
 real   56m1.546s

I then created a new vos-backup, and everything looks fine.  And now I'm 
11 gigabytes closer to retiring our older file servers!  One slightly 
odd thing is that the 11 gigabytes did not disappear from "Used" disk 
space on the old server until hours later.  But it did eventually 
disappear, so I'm all set.


Thanks again.

--
Garance Alistair Drosehn= dro...@rpi.edu
Senior Systems Programmer   or   g...@freebsd.org
Rensselaer Polytechnic Institute; Troy, NY;  USA
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info