From what I could gather the "invalid volume id" bug was first a patch
and then rolled in to 1.4.14
Built/installed 1.4.14 on one of two file servers in a test cell.
Doesn't seem to be working, still getting "invalid volume ID" error
jplis-fil-krb03 root > strings /usr/afs/bin/salvager | grep built
@(#) OpenAFS 1.4.14 built 2011-03-08
jplis-fil-krb03 root > /usr/afs/bin/salvager /vicepa 3249855668
jplis-fil-krb03 root > tail -f /usr/afs/logs/SalvageLog
@(#) OpenAFS 1.4.14 built 2011-03-08
03/09/2011 13:42:41 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager
/vicepa 3249855668)
03/09/2011 13:42:41 salvage: invalid volume id specified; salvage aborted
jplis-fil-krb03 root > vos exa 3249855668
highID.eraseme2 3249855668 RW 5 K On-line
jplis-fil-krb03.jpl.nasa.gov /vicepa
RWrite 3249855668 ROnly 0 Backup 0
MaxQuota 0 K
Creation Wed Mar 9 13:40:22 2011
Copy Wed Mar 9 13:41:43 2011
Backup Wed Dec 2 14:36:16 2009
Last Update Wed Dec 28 23:26:47 2005
0 accesses in the past day (i.e., vnode references)
RWrite: 3249855668
number of sites -> 1
server jplis-fil-krb03.jpl.nasa.gov partition /vicepa RW Site
jplis-fil-krb03 root >
Odd.
Kim
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
