Re: [zfs-discuss] dedup status

2010-10-01 Thread Markus Kovero
Hi! > Hi all > I just tested dedup on this test box running OpenIndiana (147) storing bacula > backups, and did some more testing on some datasets with ISO images. The > > results show so far that removing 30GB deduped datasets are done in a matter > of minutes, which is not the case with 134

Re: [zfs-discuss] dedup status

2010-09-30 Thread Dave
Can you provide some specifics to see how bad the writes are? -- This message posted from opensolaris.org ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] dedup status

2010-05-20 Thread George Wilson
Roy Sigurd Karlsbakk wrote: Hi all I've been doing a lot of testing with dedup and concluded it's not really ready for production. If something fails, it can render the pool unuseless for hours or maybe days, perhaps due to single-threded stuff in zfs. There is also very little data available

Re: [zfs-discuss] dedup status

2010-05-16 Thread Erik Trimble
Roy Sigurd Karlsbakk wrote: - "Haudy Kazemi" skrev: In this file system, 2.75 million blocks are allocated. The in-core size of a DDT entry is approximately 250 bytes. So the math is pretty simple: in-core size = 2.63M * 250 = 657.5 MB If your dedup ratio is 1.0, then this number

Re: [zfs-discuss] dedup status

2010-05-16 Thread Roy Sigurd Karlsbakk
- "Haudy Kazemi" skrev: > In this file system, 2.75 million blocks are allocated. The in-core > size > of a DDT entry is approximately 250 bytes. So the math is pretty > simple: > in-core size = 2.63M * 250 = 657.5 MB > > If your dedup ratio is 1.0, then this number will scale linearl

Re: [zfs-discuss] dedup status

2010-05-16 Thread Haudy Kazemi
Erik Trimble wrote: Roy Sigurd Karlsbakk wrote: Hi all I've been doing a lot of testing with dedup and concluded it's not really ready for production. If something fails, it can render the pool unuseless for hours or maybe days, perhaps due to single-threded stuff in zfs. There is also very

Re: [zfs-discuss] dedup status

2010-05-16 Thread Roy Sigurd Karlsbakk
- "Erik Trimble" skrev: > Roy Sigurd Karlsbakk wrote: > > Hi all > > > > I've been doing a lot of testing with dedup and concluded it's not > really ready for production. If something fails, it can render the > pool unuseless for hours or maybe days, perhaps due to single-threded > stuff in z

Re: [zfs-discuss] dedup status

2010-05-16 Thread Markus Kovero
Hi, its getting better, I believe its no longer single threaded after 135? (http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6922161) but still waiting for major bug fix, http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6924824 It should be fixed before Release afaik. Yours

Re: [zfs-discuss] dedup status

2010-05-15 Thread Erik Trimble
Roy Sigurd Karlsbakk wrote: Hi all I've been doing a lot of testing with dedup and concluded it's not really ready for production. If something fails, it can render the pool unuseless for hours or maybe days, perhaps due to single-threded stuff in zfs. There is also very little data available