@cmuratori It seems to me that is basically just asking to have that array (which will all be on one SSD page) get wiped out together.
-
-
Replying to @cmuratori
@cmuratori Why wouldn't you store uberblocks _strided_ across the drive instead?1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori The ZFS people seem smart so I'm wondering if I'm just not getting why it's not a problem for the uberblocks to be contiguous.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori I'm guessing uberblocks are replicated. And they are probably not striped because syncs across disks aren't transactional.4 replies 0 retweets 0 likes -
Replying to @won3d
@won3d@cmuratori (2) from same link: only *1* uberblock is actually the current valid root, you don't care what's in the other 127 anyway1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@won3d But only one of them is the current root. The other 127 are stale roots, so you don't care if you lose them.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@nothings@won3d The whole point of having the 128-array is that you need to be able to access previous ones in case of a write failure.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@nothings@won3d And that's true not just for the uberblock write, but potentially for any write underneath it...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.