I've been having a terrible time trying to move a volume back onto a server that I moved it off of.
I've been messing with it for a couple days now, and I can't seem to get around the problem. I'll set up to the next version shortly, but I haven't yet. The -fromserver is an AFS 1.4.1 server running SuSE 10.1 and the -toserver is an AFS 1.4.1 server running on SuSE 9.0. I had to move everything off the 9.0 server because the raid array had dropped one drive and a second one was shakey. Once I got that sorted out, I started trying to move some of the volumes back onto the machine. I didn't scratch and reformat the /vicepa partition, but the only volumes left on it were RO releases of root.cell and root.afs. This is the output from vos listvol before I try to move the volume. I've masked part of the names with # --------------------------------------- vos listvol endar -localauth -verbose Total number of volumes on server endar partition /vicepa: 12 home.b###### 536870942 RW 9505 K On-line home.b######.backup 536870944 BK 9505 K On-line home.d##### 536870963 RW 1542565 K On-line home.d#####.backup 536870965 BK 1542565 K On-line home.k###### 536870993 RW 4 K On-line home.k######.backup 536870995 BK 4 K On-line home.v######### 536871011 RW 184 K On-line home.v#########.backup 536871013 BK 184 K On-line home.y####### 536870984 RW 4 K On-line home.y#####.backup 536870986 BK 4 K On-line root.afs.readonly 536870913 RO 4 K On-line root.cell.readonly 536870919 RO 24 K On-line Total volumes onLine 12 ; Total volumes offLine 0 ; Total busy 0 --------------------------------------- This is the output from the vos move command... --------------------------------------- # vos move home.kdaaker -fromserver mars -frompartition /vicepa -toserver endar -topartition /vicepa -localauth -verbose Starting transaction on source volume 536870930 ... done Allocating new volume id for clone of volume 536870930 ... done Cloning source volume 536870930 ... done Ending the transaction on the source volume 536870930 ... done Starting transaction on the cloned volume 536871086 ... done Setting flags on cloned volume 536871086 ... done Getting status of cloned volume 536871086 ... done Creating the destination volume 536870930 ... Failed to create the destination volume 536870930 : Input/output error vos move: operation interrupted, cleanup in progress... clear transaction contexts Recovery: Releasing VLDB lock on volume 536870930 ... done Recovery: Ending transaction on clone volume ... done Recovery: Accessing VLDB. move incomplete - attempt cleanup of target partition - no guarantee Recovery: Creating transaction for destination volume 536870930 ... Recovery: Unable to start transaction on destination volume 536870930. Recovery: Creating transaction on source volume 536870930 ... done Recovery: Setting flags on source volume 536870930 ... done Recovery: Ending transaction on source volume 536870930 ... done Recovery: Creating transaction on clone volume 536871086 ... done Recovery: Deleting clone volume 536871086 ... done Recovery: Ending transaction on clone volume 536871086 ... done Recovery: Releasing lock on VLDB entry for volume 536870930 ... done cleanup complete - user verify desired result --------------------------------------- >From FileLog Thu Sep 21 15:48:43 2006 File Server started Thu Sep 21 15:48:43 2006 Thu Sep 21 15:59:09 2006 VAttachVolume: Failed to open /vicepa//V0536870930.vol (errno 2) --------------------------------------- >From VolserLog Thu Sep 21 15:48:44 2006 Starting AFS Volserver 2.0 (/usr/lib/openafs/volserver) Thu Sep 21 15:59:43 2006 VAttachVolume: Failed to open /vicepa/V0536870930.vol (errno 2) Thu Sep 21 15:59:43 2006 1 Volser: CreateVolume: Unable to create the volume; aborted, error code 103 Thu Sep 21 15:59:43 2006 : Software caused connection abort Thu Sep 21 15:59:44 2006 VAttachVolume: Error reading volume header /vicepa/V0536870930.vol --------------------------------------- I think the problem has something to do with something that shows up when I salvage the partition. I've tried getting rid of the bogus.536870930 volume with vos remove and vos zap, and it always comes back after a salvage. This is from the SalvageLog -------------------------------- 09/21/2006 15:48:37 SALVAGING VOLUME 536870930. 09/21/2006 15:48:37 bogus.536870930 (536870930) not updated (created 09/20/2006 21:35) 09/21/2006 15:48:37 No header file for volume 536870930 09/21/2006 15:48:37 No header file for volume 536870930; creating /vicepa/V0536870930.vol 09/21/2006 15:48:37 totalInodes 5 09/21/2006 15:48:37 iinc failed. inode 1550680829470066 errno 9 09/21/2006 15:48:37 iinc failed on link table, errno = 9 09/21/2006 15:48:37 iinc failed on link table, errno = 9 09/21/2006 15:48:37 Salvaged bogus.536870930 (536870930): 0 files, 0 blocks -------------------------------- Thanks. Ken Aaker _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
