In case, there are libraries backed by SMB shares with content on vCenter Server during the upgrade, perform the following steps to recover the content of such libraries after upgradeing.
select lib.id, lib.name, storage.storageuri from cl_library lib, cl_library_storage lib_storage, cl_storage storage where lib.id = lib_storage.library_id and lib_storage.storage_id = storage.id and storage.storageuri like 'file:///etc/vmware-content-library/winmounts/library-win-mount%';
id | name | storageuri
--------------------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------
########-####-####-####-##########88 | smblib | file:///etc/vmware-content-library/winmounts/library-win-mount-########-####-####-####-##########88-ClsPathSeparator-smb://hostname.example.com/storage/cl_qe/smbBackupMount/
echo "file:///etc/vmware-content-library/winmounts/library-win-mount-########-####-####-####-##########88-ClsPathSeparator-smb://hostname.example.com/storage/cl_qe/smbBackupMount/" | sed 's/file:\/\/\(.*\)-ClsPathSeparator-smb:.*/\1/'
/etc/vmware-content-library/winmounts/library-win-mount-########-####-####-####-##########88
mount | grep "/etc/vmware-content-library/winmounts/library-win-mount-########-####-####-####-##########88"
If this command returns no entry (null), it means the library is consuming storage space from the vCenter server, and then add it to the SMB library list.