[OpenAFS] 'vos dump VOLUME.backup' locks VOLUME, not VOLUME.backup!

[Derek Atkins]

Turbo,

One problem in your script is that you only "vos backup" the first
time.  The second time you try to dump a volume you do NOT "vos
backup".

That is a bug.  You want to "vos backup" every time you run through
the script!  Otherwise you will never dump current data.  The reason
for my saying this is that the backup volume (created by vos backup or
vos backupsys) is just a volume clone made at the time.  As the user
changes data, the backup volume will maintain the original state at
the time of the backup.  So, you want to freshen the backup volume
before you dump it.

Another bug in your script is that you shouldn't need the -server and
-partition fields for the backup volume.  You should be able to just
use:
        vos dump "$volume".backup -file $BACKUPFILE

This combination might be affecting you.

-derek

Turbo Fredriksson <turbo@bayour.com> writes:

> >>>>> "Hartmut" == Hartmut Reuter <reuter@rzg.mpg.de> writes:
> 
>     >>  It's a small volume (163Mb), but it locks for about 10
>     >> minutes...  Shouldn't the lock be ONLY for the number of
>     >> seconds it takes for 'vos backup' to finish?
> 
>     Hartmut> The being busy and locked ends when the command "vos
>     Hartmut> backup" has finished.
> 
> Dang, that sucks!
> 
>     Hartmut> Are you sure you are dumping really the backup volume not
>     Hartmut> the RW-volume?
> 
> Yes, have a look you self http://www.bayour.com/scripts/backup_afs.sh
> 
> -- 
> 747 pits Kennedy jihad Panama quiche AK-47 radar Peking colonel
> Serbian South Africa Marxist spy $400 million in gold bullion
> [See http://www.aclu.org/echelonwatch/index.html for more about this]
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info

-- 
       Derek Atkins
       Computer and Internet Security Consultant
       derek@ihtfp.com             www.ihtfp.com