I've noticed that with the update v2.03 the P2P map isn't accessible anymore from the Volume_1 folder over samba. It can still be shared separately but this is inconvenient if you want to move a file from P2P to an other map.
Because both maps are different samba-shares, this will be interpreted as a copy and not a move. This implies that instead of an instantaneous move it will take a long time as a copy.
I've found the problem in the samba.conf file. It uses a line called "veto files" in which the map P2P is mentioned.
I can remove it for certain cases using the funplug pack, but as soon as I add or delete a samba share through the http interface, it resets this samba.conf and also resets the veto files.
Is there some way I can remove this permanently or can it be 'fixed' in the next firmware update?