[OpenAFS] Re: Vos move/release failure

[Sidney Cammeresi]

On Sun, 04 Apr 2010 at 13.21.07 -0400, Derrick Brashear wrote:
> On Sun, Apr 4, 2010 at 7:00 AM, Sidney Cammeresi <sac@cheesecake.org> w=
rote:
> > One of my fileservers is returning errors when I try to move or relea=
se
> > certain volumes to it. =A0For example,
> >
> > ----------
> >
> > $ vos ex test
> > test =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A053687=
1126 RW =A0 =A0 =A0 =A0 =A02 K =A0On-line
> > =A0 =A0good /vicepa
> > =A0 =A0RWrite =A0536871126 ROnly =A0536871133 Backup =A0 =A0 =A0 =A0 =
=A00
> > =A0 =A0MaxQuota =A0 =A0 =A0 5000 K
> > =A0 =A0Creation =A0 =A0Sun Apr =A04 12:40:27 2010
> > =A0 =A0Copy =A0 =A0 =A0 =A0Sun Apr =A04 12:41:53 2010
> > =A0 =A0Backup =A0 =A0 =A0Never
> > =A0 =A0Last Update Never
> >
> > =A0 =A0RWrite: 536871126
> > =A0 =A0number of sites -> 1
> > =A0 =A0 =A0 server good partition /vicepa RW Site
> > $ vos move test good a bad a
> >
> > Failed to move data for the volume 536871126
> > =A0 : No such file or directory
> > vos move: operation interrupted, cleanup in progress...
> > clear transaction contexts
> > move incomplete - attempt cleanup of target partition - no guarantee
> > cleanup complete - user verify desired result
> >
> > ----------
> >
> > All I see in VolserLog on the bad server is
> >
> > Sun Apr =A04 12:50:09 2010 VAttachVolume: Failed to open /vicepa/V053=
6871126.vol (errno 2)
> > Sun Apr =A04 12:50:09 2010 1 Volser: CreateVolume: volume 536871126 (=
test) created
> > Sun Apr =A04 12:50:12 2010 1 Volser: Delete: volume 536871126 deleted
> >
> >
> >
> > I deleted the volume "test," and then I performed this sequence of
> > commands to get a different failure:
> >
> > ----------
> >
> > $ vos create bad a test
> > Volume 536871134 created on partition /vicepa of bad
> > $ vos addsite bad a test
> > Added replication site bad /vicepa for volume test
> > $ vos addsite good a test
> > Added replication site good /vicepa for volume test
> > $ vos release test
> > Released volume test successfully
> > $ vos move test bad a good a
> > WARNING : readOnly copies still exist
> > Volume 536871134 moved from bad /vicepa to good /vicepa
> > $ vos release test
> > Release failed: VOLSER: Problems encountered in doing the dump !
>=20
> So you gave us one log. There are 2 servers in play. How about that oth=
er log?

If I do the create, addsite, addsite, release sequence that I previously
described, I get the following in the VolserLog on the good server:

Mon Apr  5 09:05:17 2010 1 Volser: CreateVolume: volume 536871141 (test) =
created
Mon Apr  5 09:06:19 2010 1 Volser: Clone: Cloning volume 536871141 to new=
 volume 536871142

and the following in the VolserLog on the bad server:

Mon Apr  5 09:06:27 2010 VAttachVolume: Failed to open /vicepa/V053687114=
2.vol (errno 2)
Mon Apr  5 09:06:27 2010 1 Volser: CreateVolume: volume 536871142 (test.r=
eadonly) created

Regarding other suggestions I've received, I've tried running bos salvage=
,
which had no effect, and I have tried running vos release -v, which provi=
ded
this output:

test
    RWrite: 536871141     ROnly: 536871142     RClone: 536871142
    number of sites -> 3
       server good partition /vicepa RW Site  -- New release
       server good partition /vicepa RO Site  -- New release
       server bad partition /vicepa RO Site  -- Old release
This is a completion of a previous release
Starting transaction on cloned volume 536871142... done
Updating existing ro volume 536871142 on bad ...
Starting ForwardMulti from 536871142 to 536871142 on bad (full release).
Failed to dump volume from clone to a ro site: : No such file or director=
y
The volume 536871141 could not be released to the following 1 sites:
                     bad /vicepa
VOLSER: release could not be completed
Error in vos release command.
VOLSER: release could not be completed

--=20
Sidney August Cammeresi IV
http://www.cheesecake.org/sac/