[2227] in SIPB-AFS-requests
Re: sipb cell volume release errors
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Jan 8 05:53:35 1996
To: sipb-afsreq@MIT.EDU
In-Reply-To: Your message of "Mon, 08 Jan 1996 04:50:36 EST."
<9601080950.AA01099@ronald-ann2.MIT.EDU>
Date: Mon, 08 Jan 1996 05:53:19 EST
From: Greg Hudson <ghudson@MIT.EDU>
> Old read only clone is not accesible, try releasing volume 536872146 with -f flag
> VOLSER: no such volume - location specified incorrectly or volume does not exist
> Error in vos release command
> Old read only clone is not accesible, try releasing volume 536872146 with -f flag
> VOLSER: no such volume - location specified incorrectly or volume does not exist
> Error in vos release command
I ran vos release with the -f flag, apparently clearing up this
problem. I think this happened because the product of a previous "vos
release" wound up in rosebud's root filesystem and was blown away.
I'm not sure why this didn't happen to the four other volumes in the
same situation.
I also noticed that contrib had a replication site on
ronald-ann:/vicepe, while the read-write resided on
ronald-ann:/vicepd. I moved the ronald-ann replication site to
vicepd.
