On Thursday 19 March 2009 14:48, Jeffrey Altman wrote: > McKee, Shawn wrote: > > Thanks Jeffrey, > > > > Yes, I agree...you have found the issue. I am surprised no one else has > > hit this before (maybe they have but I didn't find this problem in my > > searching). > > > > I guess this will take a patch to the code for existing versions to get > > this resolved. > > > > Thanks again, > > > > Shawn > > I have opened ticket 124510 for this issue.
I want to point out that in the past the issue of volumes with "too large" ID emerged also in our cell (enea.it). At that time (2002) we still had AFS Transarc and the support provided us with a patched AFS version, able to operate with volumes having "too large" IDs. Before migrating to OpenAFS we had to recover the normal AFS behaviour and the procedure we did at that time (2005) was described at AFS & Kerberos Best Practices Workshop 2005 in Pittsburgh http://workshop.openafs.org/afsbpw05/talks/VirtualAFScell_Bracco_Pittsburgh2005.pdf. At that time it was not clear the reason of the initial problem. Do have I to assume that now it has been identified? Giovanni -- Giovanni Bracco ENEA FIM (Servizio Informatica e Reti) Via E. Fermi 45 I-00044 Frascati (Roma) Italy phone 00-39-06-9400-5597 FAX 00-39-06-9400-5735 E-mail bra...@frascati.enea.it WWW http://www.afs.enea.it/bracco _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info