@cmuratori @won3d As you go back further, ever more stuff will have been recycled. According to the link, ZFS won't even try recovering > 3.
-
-
Replying to @nothings
@cmuratori@won3d Anyway, I have no idea why you're drilling down into this since (1) should have answered your question satisfactorily.1 reply 0 retweets 0 likes -
Replying to @cmuratori
(BLM) Sean Barrett Retweeted (BLM) Sean Barrett
@cmuratori@won3d Dude, how many tweets ago did I say "you're right"?!? https://twitter.com/nothings/status/390956570609057792 … (7)(BLM) Sean Barrett added,
1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@won3d Dude, I said "that doesn't work ONCE [the relevant] FREE SPACE gets recycled". This is true & described in detail at link!1 reply 0 retweets 0 likes -
Replying to @cmuratori
@nothings@won3d And "relevant" in this case is very specific. It has to be _very_ high in the tree before you wouldn't care _at all_.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@nothings@won3d And furthermore, that is very unlikely to happen because those nodes would not have been marked free until after the write.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@nothings@won3d In other words, the chance that a new uberblock's tree uses free space from the previous uberblock's tree _is zero_.1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.