Just in case someone else comes across this post, VMware have now confirmed that it's a bug in the upgrade procedure. The KB article hasn't been published yet but it's caused by a space in the NFS datastore name and apparently it only affects ESX classic. I've written up details in a blogpost;
http://www.vexperienced.co.uk/?p=1778
Regards,
Ed.
