not related to partitions currently assigned to a storage node. This is required
because an old node can come back, get a new UUID, start replication and a
conflict on (oid, serial) with the cluster it is joining. As there is now check
on the object integrity, the object will not be replicated and a bad object will
be kept. So during storage initialization, after getting the full partition
table, a storage look if there is partitions unassigned to it and drop data for
those partitions.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1228 71dcc9de-d417-0410-9af5-da40c76e7ee4