> > At first we blamed de-dupe, but we've disabled that. Next we > suspected > > the SSD log disks, but we've seen the problem with those removed, as > > well. > > Did you have dedup enabled and then disabled it? If so, data can (or > will) be deduplicated on the drives. Currently the only way of de- > deduping them is to recopy them after disabling dedup.
That's a good point. There is deduplicated data still present on disk. Do you think the issue we're seeing may be related to the existing deduped data? I'm not against copying the contents of the pool over to a new pool, but considering the effort/disruption I'd want to make sure it's not just a shot in the dark. If I don't have a good theory in another week, that's when I start shooting in the dark... -Charles _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
