Question about FSHammer getting full
Simon 'corecode' Schubert
corecode at fs.ei.tum.de
Fri Aug 28 16:04:00 PDT 2009
Matthew Dillon wrote:
:I think it is not as easy, because we want the current state to be the
:reference, and have the usage of the snapshots show what would be free'd
:when the snapshot was removed. So old, unmodfied data has to be charged
:to the current usage and not to the snapshot that first contained it.
That's actually very easy to do, because you extracting the information
based on the *DELETE* transaction id, not the *CREATE* transaction id.
If the information is not deleted (delete_tid is 0), then it is current
information regardless of how long ago it was created.
What about overlapping regions?
the OLD won't have a delete_tid != 0. Or will hammer split up the
extent into smaller pieces when the new one comes in?
<3 the future +++ RENT this banner advert +++ ASCII Ribbon /"\
rock the past +++ space for low CHF NOW!1 +++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
More information about the Users