Deleting too fast


Here’s an interesting side effect that came up in Hammer 2 development: deleting files can potentially require modification of only one parent element.  If I’m reading it right, that means deletion always takes about the same time, independent of the amount of data being deleted.  Your ‘rm -rf /largedrive’ could complete, removing multiple terabytes of data before you realize it.  I suppose it’s silly to complain about speedy results.  Of course, being Hammer, it would still be available in history.

 

Posted by     Categories: Committed Code, DragonFly, Hammer     0 Comments
0 Comments on Deleting too fast

Respond | Trackback

Respond

Comments

Comments