Re: new RW root.cell

Hmm.. I moved removed the incorrect RO and created a new RO on velma, then
tried to 'release' the new one prior to moving it to a different server and
that doesn't work.  I'm hesitant to go ahead and move it if it's not in a
good state.

*STATE BEFORE: *
[root@afs-vmc 2019-March]# vos volinfo root.cell
vsu_ClientInit: Could not get afs tokens, running unauthenticated.
root.cell                         537176384 RW         49 K  On-line
    velma.psc.edu /vicepca
    RWrite  537176384 ROnly          0 Backup  537176401
    MaxQuota      20000 K
    Creation    Tue Nov 29 19:01:08 2005
    Copy        Fri Jun  8 16:24:57 2012
    Backup      Sat Mar  2 02:32:38 2019
    Last Access Thu Mar  7 11:49:29 2019
    Last Update Thu Apr  5 14:20:25 2018
    266 accesses in the past day (i.e., vnode references)

    RWrite: 537176384     ROnly: 537176385     Backup: 537176401
    number of sites -> 5
       server velma.psc.edu partition /vicepca RW Site
       server daphne.psc.edu partition /vicepdc RO Site
       server velma.psc.edu partition /vicepcb RO Site
       server scooby.psc.edu partition /vicepac RO Site
       server afs-vmc.psc.edu partition /vicepga RO Site  -- Not released
[root@afs-vmc 2019-March]# *vos remsite velma.psc.edu
<http://velma.psc.edu> vicepcb root.cell -localauth *
Deleting the replication site for volume 537176384 ...Removed replication
site velma.psc.edu /vicepcb for volume root.cell
[root@afs-vmc 2019-March]# *vos addsite velma.psc.edu
<http://velma.psc.edu> vicepca root.cell -localauth *
Added replication site velma.psc.edu /vicepca for volume root.cell

*STATE AFTER: *
[root@afs-vmc 2019-March]# vos volinfo root.cell
vsu_ClientInit: Could not get afs tokens, running unauthenticated.
root.cell                         537176384 RW         49 K  On-line
    velma.psc.edu /vicepca
    RWrite  537176384 ROnly          0 Backup  537176401
    MaxQuota      20000 K
    Creation    Tue Nov 29 19:01:08 2005
    Copy        Fri Jun  8 16:24:57 2012
    Backup      Sat Mar  2 02:32:38 2019
    Last Access Thu Mar  7 11:49:29 2019
    Last Update Thu Apr  5 14:20:25 2018
    266 accesses in the past day (i.e., vnode references)

    RWrite: 537176384     ROnly: 537176385     Backup: 537176401
    number of sites -> 5
       server velma.psc.edu partition /vicepca RW Site
       server daphne.psc.edu partition /vicepdc RO Site
       server scooby.psc.edu partition /vicepac RO Site
       server afs-vmc.psc.edu partition /vicepga RO Site  -- Not released
       server velma.psc.edu partition /vicepca RO Site  -- Not released


[root@afs-vmc 2019-March]# *vos release root.cell -localauth*
Failed to clone the volume 537176384
: Invalid cross-device link
Error in vos release command.
Clone volume is not in the same partition as the read-write volume.




On Thu, Mar 7, 2019 at 11:39 AM Benjamin Kaduk <[email protected]> wrote:

> On Thu, Mar 07, 2019 at 11:29:23AM -0500, Susan Litzinger wrote:
> > In order to get our current installation in sync, I attempted to create
> > another RO root.cell on velma in the same partition that the RW is on
> but I
> > am unable to do that and get the error that Multiple ROs on a single
> server
> > aren't allowed.  Will I cause problems if I remove the current RO (that
> is
> > on the wrong partition) then create a new one in the correct partition?
>
> Should not cause problems.
>
> > Then, if we move the RW root.cell to afs-vmc, the release should work?
> > Here is the results of 'vos examine root.cell' for our site:
>
> Assuming you move it to afs-vmc's vicepga, that should work.
>
> -Ben
>
> > [root@afs-vmc 2019-March]# vos examine root.cell
> > vsu_ClientInit: Could not get afs tokens, running unauthenticated.
> > root.cell                         537176384 RW         49 K  On-line
> >     velma.psc.edu /vicepca
> >     RWrite  537176384 ROnly          0 Backup  537176401
> >     MaxQuota      20000 K
> >     Creation    Tue Nov 29 19:01:08 2005
> >     Copy        Fri Jun  8 16:24:57 2012
> >     Backup      Sat Mar  2 02:32:38 2019
> >     Last Access Thu Mar  7 10:43:30 2019
> >     Last Update Thu Apr  5 14:20:25 2018
> >     239 accesses in the past day (i.e., vnode references)
> >
> >     RWrite: 537176384     ROnly: 537176385     Backup: 537176401
> >     number of sites -> 5
> >        server velma.psc.edu partition /vicepca RW Site
> >        server daphne.psc.edu partition /vicepdc RO Site
> >        server velma.psc.edu partition /vicepcb RO Site
> >        server scooby.psc.edu partition /vicepac RO Site
> >        server afs-vmc.psc.edu partition /vicepga RO Site  -- Not
> released
> >
> > Thanks for the help -- Susan
> >
> >
> > On Wed, Mar 6, 2019 at 6:11 PM Jeffrey Altman <[email protected]>
> wrote:
> >
> > > On 3/6/2019 3:56 PM, Susan Litzinger wrote:
> > > > We are updating our very old AFS servers and chose to create new,
> > > > updated systems then migrate all the volumes over and eventually just
> > > > turn the older ones off.
> > > >
> > > > We've moved everything but the root.cell volumes.  We have one RW
> > > > root.cell on an older server and would like to have a RW root.cell
> on a
> > > > new server before turning the older one off.  My co-worker gave this
> a
> > > > try and it allowed her to run 'vos addsite' but did not allow her to
> > > > 'vos release' the new RW root.cell.  She got this error:
> > > >
> > > > root@afs-vmc 2019-March]# vos addsite afs-vmc.psc.edu
> > > > <http://afs-vmc.psc.edu> /vicepga
> > > > root.cell -localauth
> > > > Added replication site afs-vmc.psc.edu <http://afs-vmc.psc.edu>
> /vicepga
> > > > for volume root.cell
> > > > [root@afs-vmc 2019-March]# vos release root.cell -localauth
> > > > Failed to clone the volume 537176384
> > > > : Invalid cross-device link
> > > > Error in vos release command.
> > > > Clone volume is not in the same partition as the read-write volume.
> > >
> > >
> > > Susan,
> > >
> > > The problem with root.cell is on velma.  The RW and RO must be on the
> > > same partition.
> > >
> > > Jeffrey Altman
> > >
> > >
>