Matthew Sakai

Thank you for reporting this. It is indeed a typo. It will be fixed in the next update. The line is merely informational, so you can ignore it. As you...

I was going to just fix the typo, but on reflection the extra output isn't very useful, so I will remove it. The $$ appears to have been a simple...

I tried to respond to this yesterday, but apparently I haven't figured out the right technique for replying by mail. I think there are really only a few options. Either...

[removed duplicate comment] I'm not sure why this comment got reposted; I did not intend to do that.

@sweettea, that reuse scenario is prevented by dedupeContext->requestState. Even when a data_vio is reused for a subsequent write, its dedupe_context is not (and cannot be) reused until the index request...

This changes looks reasonable, but we're currently in the process of rearranging how this project is organized and this may not be the right branch to incorporate this. I'll try...

This is due to the way that the index size requirements are specified. The vdo_index_memory_size_mb parameter represent the amount of memory (RAM) that the index requires. Using 3072 means that...

> > Out of space here means that your device does not have enough space for the layout that VDO tries to create. > > Oh okay... Didn't have any...

The problem you're running into here is that each physical thread needs to have an least one slab available. The size of your volume is 12GB, which it only enough...

> About threads, my reasoning was to say: by default, this setting has 1 thread, this one has 2 and this one has 4; so I'll take the number of...