Hello,
I just tried to deploy 1.6.1a on linux, migrating from 1.4 server. I
compiled from tar.gz sources and copied executables to /usr/afs/bin
This operation has put all my volumes offline with the following FileLog
entries:
Wed Sep 19 13:54:48 2012 GetBitmap: addled vnode index in volume
q.afs.st.afs211.fb.1; volume needs salvage
Wed Sep 19 13:54:48 2012 VAttachVolume: error getting bitmap for volume
(/vicepfb/V1934450230.vol)
Wed Sep 19 13:54:48 2012 ReadHeader: Failed to open volume info header
file (volume=1934450242, inode=8308400533853437951); errno=2
Wed Sep 19 13:54:48 2012 VAttachVolume: Error reading diskDataHandle
header for vol 1934450244; error=101
Wed Sep 19 13:54:48 2012 VAttachVolume: Error attaching volume
/vicepfb/V1934450244.vol; volume needs salvage; error=101
I then tried to salvage one of the volumes with the following salvager
errors:
09/19/2012 13:34:10 SYNC_ask: negative response on circuit 'FSSYNC'
09/19/2012 13:34:10 FSYNC_askfs: FSSYNC request denied for reason=101
09/19/2012 13:34:10 AskOnline: file server denied online request to
volume 1934450244 partition /vicepfb; trying again...
Finally another salvage attempt on the same volume corrupted it and left
it at 0KB:
(#) OpenAFS 1.6.1a built 2012-09-19
09/19/2012 13:56:14 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager
/vicepfb 1934450242 -showlog -orphans remove)
09/19/2012 13:56:14 1 nVolumesInInodeFile 32
09/19/2012 13:56:14 SALVAGING VOLUME 1934450242.
09/19/2012 13:56:14 q.afs.st.afs211.fb.3 (1934450242) updated 08/21/2012
14:07
09/19/2012 13:56:14 totalInodes 4
09/19/2012 13:56:14 Salvaged q.afs.st.afs211.fb.3 (1934450242): 0 files,
0 blocks
09/19/2012 13:56:14 The volume header file /vicepfb/V1934450244.vol is
not associated with any actual data (deleted)
Is there some special procedure to be applied for the migration?
Many thanks,
--
Best regards,
Jakub Moscicki
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
