[OpenAFS-devel] CopyOnWrite failure

[Todd_DeSantis@transarc.com]

Hi Marco -

Thanks for the information that you sent.  Another piece of debugging
data that might be useful would be a volinfo snapshot of the corrupted
volume.  If you are not familiar with the volinfo binary, it is
usually placed in the

  root.server/usr/afs/bin  area

and in this case, we would run it as root on the fileserver machine

# /usr/afs/bin/volinfo -part /vicepa -volum 536875505 -vnode -inode \
	-header > /tmp/volinfo.536875505

This command can give us information on the data in the volume.
Sometimes it can help us troubleshoot problems in this area.

With the -vnode option, it will generate a substantial amount of data
because it outputs information on each vnode in the volume going
through the small and large vnode arrays.  The more fiels and
directories in the volume, the more data.

Thanks for your help

Todd