Volume and file system manager metadata out of sync

My netbook did not want to download the files from /home/rtg/Documents UDF:

rtg@buka:~/ubuntuone-client/contrib$ u1sdtool --list-folders
Folder list:
  id=a19bb966-a0e9-4f05-a927-f9fc81986258 subscribed=True path=/home/rtg/.ubuntuone/Purchased from Ubuntu One
  id=20b0b044-523f-462a-8938-7e2fa16030b0 subscribed=True path=/home/rtg/Public
  id=5577d808-6a3f-4873-8b27-1fd644bd7e20 subscribed=True path=/home/rtg/Documents

rtg@buka:~/ubuntuone-client/contrib$ u1sdtool --info /home/rtg/Documents/

Oops, an error ocurred:
Traceback (most recent call last):
Failure: dbus.exceptions.DBusException: org.freedesktop.DBus.Python.KeyError: Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/service.py", line 702, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/pymodules/python2.6/ubuntuone/syncdaemon/dbus_interface.py", line 968, in get_metadata
    mdobj = self.fs_manager.get_by_path(path.encode('utf-8'))
  File "/usr/lib/pymodules/python2.6/ubuntuone/syncdaemon/filesystem_manager.py", line 587, in get_by_path
    mdid = self._idx_path[path]
KeyError: '/home/rtg/Documents'

When I tried unsubscribing/subscribing, the subscription failed with
rtg@buka:~/ubuntuone-client/contrib$ u1sdtool --subscribe=5577d808-6a3f-4873-8b27-1fd644bd7e20
FolderSubscribeError: METADATA_DOES_NOT_EXIST (id=5577d808-6a3f-4873-8b27-1fd644bd7e20)

Full discussion: http://irclogs.ubuntu.com/2010/09/07/%23ubuntuone.html#t15:24
<rye> verterok, thanks! Should I file bug about that? Unfortunately I have no idea about how that could have happened, though
<verterok> rye: my guess is corrupted/broken FSM metadata, but it's just a guess
 rye: yes, we should have a bug
 rye: the title might be something like: volume and filesystem manager metadata out of sync(?)
<verterok> facundobatista: ^ any ideas :)
* dendro-afk is now known as dendrobates
<facundobatista> verterok, yes, a bug, and the fix for it will be VM assuring it has the node in FSM
<verterok> facundobatista: yes, VM assumes the node is there since it was created when the UDF was created, I'll take a look at where we can check for the fsm node

WORKAROUND:
1) Shut down ubuntuone-syncdaemon
2) Delete an UDF node metadata in ~/.local/share/ubuntuone/syncdaemon/vm/udfs/ (in my case - 5/5/5577... file)
3) Start syncdaemon again