On Mon, 05 Apr 2010 at 07.56.19 -0400, Derrick Brashear wrote: > On Mon, Apr 5, 2010 at 3:12 AM, Sidney Cammeresi <[email protected]> wrote: > > On Sun, 04 Apr 2010 at 13.21.07 -0400, Derrick Brashear wrote: > >> On Sun, Apr 4, 2010 at 7:00 AM, Sidney Cammeresi <[email protected]> > >> wrote: > >> > One of my fileservers is returning errors when I try to move or release > >> > certain volumes to it. For example, > >> > > >> > ---------- > >> > > >> > $ vos ex test > >> > test 536871126 RW 2 K On-line > >> > good /vicepa > >> > RWrite 536871126 ROnly 536871133 Backup 0 > >> > MaxQuota 5000 K > >> > Creation Sun Apr 4 12:40:27 2010 > >> > Copy Sun Apr 4 12:41:53 2010 > >> > Backup Never > >> > Last Update Never > >> > > >> > RWrite: 536871126 > >> > number of sites -> 1 > >> > server good partition /vicepa RW Site > >> > $ vos move test good a bad a > >> > > >> > Failed to move data for the volume 536871126 > >> > : 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 4 12:50:09 2010 VAttachVolume: Failed to open > >> > /vicepa/V0536871126.vol (errno 2) > >> > Sun Apr 4 12:50:09 2010 1 Volser: CreateVolume: volume 536871126 (test) > >> > created > >> > Sun Apr 4 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 ! > >> > >> So you gave us one log. There are 2 servers in play. How about that other > >> 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/V0536871142.vol (errno 2) > > Mon Apr 5 09:06:27 2010 1 Volser: CreateVolume: volume 536871142 > > (test.readonly) created > > Yeah, but you're still not telling us about the source server's log > during the release to the "bad" server. What appears in the good > server's log at 9:06:27? > > What OpenAFS versions are in play, again?
Sorry for omitting the OpenAFS versions. Initially the good machine was running 1.4.2, but I have upgraded it to Lenny and the corresponding package of 1.4.7. The bad machine is also running Lenny's 1.4.7. There was nothing in the good server's log at 9:06:27. Testing again, I see on good: VolserLog Mon Apr 5 16:02:28 2010 1 Volser: Clone: Recloning volume 536871151 to volume 536871152 FileLog Mon Apr 5 16:02:28 2010 fssync: volume 536871152 restored; breaking all call backs And on bad: VolserLog Mon Apr 5 16:02:36 2010 VAttachVolume: Failed to open /vicepa/V0536871152.vol (errno 2) Mon Apr 5 16:02:36 2010 1 Volser: CreateVolume: volume 536871152 (test.readonly) created There is nothing in the good server's logs at 16:02:36. -- Sidney August Cammeresi IV http://www.cheesecake.org/sac/ _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
