Well I run an open sand box, so they came to my grid and rezzed items, not all at once, but one after another. It all got stored in my grid asset server and my drives ran out of space and my grid crashed. So I used sql commands and removed all objects entered after that date. This fixed my inventory and asset server. Then I went and created a new sandbox running on it's own entire standalone hypergrid. I fixed it this way and did link-region x y cyberdatastorm.com SandBox that way people can get to it from my grid. Then I set up scripts to restart the sandbox if it crashes, and if it does crash, to reset it to an empty database. Remember now it's a separate grid with it's own separate database, so i can empty it any time and nothing is lost from my actual grid. IF you have sandboxes on your grid, consider mounting them in a separate standalonehypergrid, so that your grid asset server doesn't get exploited by these bad hackers. Failing to do this opens you to the same attack that happened to me right before osgrid was attacked. Keep in mind they did not just rez a few items but hundreds of gigabytes of objects. It was almost like they created a bot that could rez very fast and delete the items after they rezzed them, thereby only filling up the asset server in a day. Whoever is doing this is very smart. I tried to trace them but they used a vpn, and probably a fake name, fake account, fake everything. So... one grid for your stuff, another grid for your sandboxes. Isolation is key.
like(2)