Fix for a dangerous bug in vol_split.c

If the volume being split has osdPolicy == 0, but has an osdMetadataHandle then
in the new created volume the vnodes didn't get the field magic filled.
If, however, the volume was created freshly on a 1.6 fileserver or moved
to it the volume to be split doesn't have an osdMetadataHandle and the vnodes
had already the correct magic. In the 1st case the salvager wouldn't load the
libafsosd extensions and would delete all the vnodes without correct magic!

Please remember: you shouldn't start an openafs-osd-1.6 fileserver for
vicep-partitions used before in an openafs-osd-1.4 fileserver. If you start using
openafs-osd-1.6 do it with empty partitions and fill them by moving the volumes
there (or creating new volumes).
Forgot to change calls ot PrintTime in this source file

Instead of the time field its address was interpreted. This showed wrong
archival and md5 sum times in "fs osd" and "fs fidosd".
Thanks to Kristen J. Webb for reproting this error!
And some more incorrect PrinTime calls

Thanks to Kristin J. Webb who reported them to me!
Avoid fetch entry reference count to stay

osd rmfetchentry returns 16 (busy) if the reference count of the fetch entry
isn't zero. Now at rxosd restart, when the fetchqueue is read in from disk, the
refcnt is reset. Also in XferData should now be no way to exit without
decrementing the reference count. I hope that will help...
Increase secondary version number of libafsosd interface

I had seen a compatibility problem in the fs- or vos-command. Just to be sure.
Please remember that you have to run configure after such a change.
Let archival disk OSDs return 'p' for HSM status

Before wiping a file the fileserver checks the HSM state to be either
'p' == premigrated or 'm' == migrated. Up to now archival disk OSDs used
to be secondary archival copies, so the problem didn't occur because the
other copy on a real HSM system showed the 'p' or 'm'. In order to make
this happen easily a new struct myOsd was introduced which contains the
fields from the OSDDB.
files generated by autotools removed
src/rxosd/rxosd.c: resolve conflict