You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature would like to see added to OpenZFS
I'd like a nice interface to lob in part or all of a file that ZFS is angy is irrevocably mangled on disk, and have it confirm "oh, yeah, that'll work" and go rewrite the affected bits, than just taking an entire send stream's data in and pulling out the germane bits.
I've been meaning to try an evil bitbanged minimal send stream emitter for this, but haven't bothered yet, so I figured I'd put it here so other people could maybe do it or follow it being done.
If I understand how corrective receive is implemented correctly, I think you could do something evil like zstream corrective-emit [various object properties] [a copy of the intact file] | zfs recv -c, and it's just a question of knowing precisely how much you need to specify versus can get elsewhere, or put it in something like zfs or zdb that actually can just go get the dataset information for a given object.
How will this feature improve OpenZFS?
Having to receive an entire 3T stream just to recover 128K of L0 is very silly.
Describe the feature would like to see added to OpenZFS
I'd like a nice interface to lob in part or all of a file that ZFS is angy is irrevocably mangled on disk, and have it confirm "oh, yeah, that'll work" and go rewrite the affected bits, than just taking an entire send stream's data in and pulling out the germane bits.
I've been meaning to try an evil bitbanged minimal send stream emitter for this, but haven't bothered yet, so I figured I'd put it here so other people could maybe do it or follow it being done.
If I understand how corrective receive is implemented correctly, I think you could do something evil like
zstream corrective-emit [various object properties] [a copy of the intact file] | zfs recv -c
, and it's just a question of knowing precisely how much you need to specify versus can get elsewhere, or put it in something likezfs
orzdb
that actually can just go get the dataset information for a given object.How will this feature improve OpenZFS?
Having to receive an entire 3T stream just to recover 128K of L0 is very silly.
Additional context
Future work section of #9372.
The text was updated successfully, but these errors were encountered: