> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Tristan Klocke
>
> I want to switch to ZFS, but still want to encrypt my data. Native Encryption
> for ZFS was added in "ZFS Pool Version Number 30", but I'm using ZFS on
> FreeBSD with Version
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Roy Sigurd Karlsbakk
>
> > > Also keep in mind that if you have an SLOG (ZIL on a separate
> > > device), and then lose this SLOG (disk crash etc), you will probably
> > > lose the pool. So if
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Tim Cook
>
> I would think a flag to allow you to automatically continue with a disclaimer
> might be warranted (default behavior obviously requiring human input).
This already exists. It's c
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Nico Williams
>
> The copies thing is a really only for laptops, where the likelihood of
> redundancy is very low
ZFS also stores multiple copies of things that it considers "extra important.
On 07/31/2012 09:46 AM, opensolarisisdeadlongliveopensolaris wrote:
> Dedup: First of all, I don't recommend using dedup under any
> circumstance. Not that it's unstable or anything, just that the
> performance is so horrible, it's never worth while. But particularly
> with encrypted data, you're g
On Tue, Jul 31, 2012 at 9:36 AM, Ray Arachelian wrote:
> On 07/31/2012 09:46 AM, opensolarisisdeadlongliveopensolaris wrote:
>> Dedup: First of all, I don't recommend using dedup under any
>> circumstance. Not that it's unstable or anything, just that the
>> performance is so horrible, it's never
On Jul 31, 2012, at 10:07 AM, Nigel W wrote:
> On Tue, Jul 31, 2012 at 9:36 AM, Ray Arachelian wrote:
>> On 07/31/2012 09:46 AM, opensolarisisdeadlongliveopensolaris wrote:
>>> Dedup: First of all, I don't recommend using dedup under any
>>> circumstance. Not that it's unstable or anything, just
> Once something is written deduped you will always use the memory when
> you want to read any files that were written when dedup was enabled, so
> you do not save any memory unless you do not normally access most of
> your data.
For reads you don't need ddt. Also in Solaris 11 (not in Illumos
unf
HI
I use GELI with ZFS all the time. Works fine for me so far.
Am 31.07.12 21:54, schrieb Robert Milkowski:
>> Once something is written deduped you will always use the memory when
>> you want to read any files that were written when dedup was enabled, so
>> you do not save any memory unless you
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Ray Arachelian
>
> One thing you can do is enable dedup when you copy all your data from
> one zpool to another, then, when you're done, disable dedup. It will no
> longer waste a ton of memor
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Richard Elling
>
> I believe what you meant to say was "dedup with HDDs sux." If you had
> used fast SSDs instead of HDDs, you will find dedup to be quite fast.
> -- richard
Yes, but this is
11 matches
Mail list logo
