OK, by replacing a RAID controller and memory, I've managed to modify the behaviour of my little file corruption issue, but magically it remains. Now it seems to be isolated to the client side -- I have yet to find a bad md4sum of a file on the server. The client-side corruption also comes and goes -- with a well-placed fs flush or flushvol, it's gone, only to reappear later. I've verified that it happens on 1.4.1 and 1.3.86 (I don't have any 1.2.x clients left to try, but I can open up the volume to the world if anybody wants to try).
cmp -l on a bad client-side file and known good file doesn't enlighten me, but maybe it will for somebody else: cmp -l aspell-pl-0.51-3.i386.rpm /tmp/aspell-pl-0.51-3.i386.rpm 13468782 337 317 cmp -l eclipse-platform-3.1.0_fc-0.M6.22.i386.rpm /tmp/eclipse-platform-3.1.0_fc-0.M6.22.i386.rpm 2883589 357 257 I can do whatever debugging will help on the file server, as it has exactly one volume on it right now. -- // Miles Davis - [EMAIL PROTECTED] - http://www.cs.stanford.edu/~miles // Computer Science Department - Computer Facilities // Stanford University _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
