Hi all
As we may know by now, the current dedup code isn't very useful. Are there work
being done on this code at the moment? If not, I think it might be a good idea
to either remove it or at least add a rather flashy warning so that people
won't use it for new systems unless they really want t
On 12/21/11 12:36, Roy Sigurd Karlsbakk wrote:
> As we may know by now, the current dedup code isn't very useful. Are there
> work being done on this code at the moment? If not, I think it might be a
> good idea to either remove it or at least add a rather flashy warning so
> that people won't use
Hi,
Roy Sigurd Karlsbakk píše v St 21. 12. 2011 v 21:36 +0100:
> Hi all
>
> As we may know by now, the current dedup code isn't very useful.
why is it not very usefull? There are setups where it is very good.
> Are there work being done on this code at the moment? If not, I think it
> might b
On 12/22/2011 07:41 AM, Milan Jurik wrote:
> Do you want to have big warning to every setup which can be problematic
> in some cases and in some not? In such case you will have warning in too
> many places.
>
> Maybe manpage can be improved to note that dedup makes sense only in
> specific setups a
Hi,
Ray Arachelian píše v čt 22. 12. 2011 v 10:36 -0500:
>
> My impression is that you can turn it on, copy your data to the zpool,
> then turn it off and not have it un-deduplicate. Maybe I'm wrong, but
> if that's the case, they'd be a much smaller memory requirement at the
> end, and you'd st
