yes, it is really bug. I will have to debub it and see why it behave this way. Maybe some missing check when starting to use storage-ng.