On Sun, Jan 1, 2012 at 12:12 AM, Niels de Carpentier
ni...@decarpentier.com wrote:
... and depending on which SSD you use, it shouldn't matter. Really.
Last time I tried with sandforce SSD + btrfs + -o discard, forcing
trim actually made things slower. Sandforce (and probably other modern
On Sat, Dec 31, 2011 at 3:12 AM, Sandra Schlichting
littlesandr...@gmail.com wrote:
How is this advantageous over dmcrypt-LUKS?
TRIM pass-through for SSD's. With dmcrypt on an SSD write performance
is very slow.
... and depending on which SSD you use, it shouldn't matter. Really.
Last time I
billycr...@gmail.com
To: Sandra Schlichting littlesandr...@gmail.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Encryption implementation like ZFS?
On Fri, Dec 30, 2011 at 14:12, Sandra Schlichting
littlesandr...@gmail.com wrote:
How is this advantageous over dmcrypt-LUKS?
TRIM pass-through
... and depending on which SSD you use, it shouldn't matter. Really.
Last time I tried with sandforce SSD + btrfs + -o discard, forcing
trim actually made things slower. Sandforce (and probably other modern
SSD) controllers can work just fine even without explicit trim fs
support.
What
The advantage of loopaes is that it is more secure then luks and way faster.
The speed with encryption (loopaes) is about 90-95% the speed without
encryption at
my setup.
Sounds very interesting. Will try that.
I case of my PC I would actually prefer a weaker encryption, as I am
not
From: linux-btrfs-ow...@vger.kernel.org [mailto:linux-btrfs-
ow...@vger.kernel.org] On Behalf Of Sandra Schlichting
TRIM pass-through for SSD's. With dmcrypt on an SSD write performance
is very slow.
That's a relative term. Suppose the SSD does 60x higher random IOPS than
the HDD, in an
... and depending on which SSD you use, it shouldn't matter. Really.
Last time I tried with sandforce SSD + btrfs + -o discard, forcing
trim actually made things slower. Sandforce (and probably other modern
SSD) controllers can work just fine even without explicit trim fs
support.
What
On Sun, Jan 1, 2012 at 12:12 AM, Niels de Carpentier
ni...@decarpentier.com wrote:
... and depending on which SSD you use, it shouldn't matter. Really.
Last time I tried with sandforce SSD + btrfs + -o discard, forcing
trim actually made things slower. Sandforce (and probably other modern
Hi everybody,
According to [0] ZFS does encryption:
One exception to this is the encryption support being added to the ZFS
filesystem. Filesystem metadata such as filenames, ownership, ACLs,
extended attributes are all stored encrypted on disk. The ZFS metadata
about the storage pool is still
On Fri, Dec 30, 2011 at 12:32, Sandra Schlichting
littlesandr...@gmail.com wrote:
According to [0] ZFS does encryption:
One exception to this is the encryption support being added to the ZFS
filesystem. Filesystem metadata such as filenames, ownership, ACLs,
extended attributes are all stored
How is this advantageous over dmcrypt-LUKS?
TRIM pass-through for SSD's. With dmcrypt on an SSD write performance
is very slow.
LUKS has always been supported between the block device and a btrfs
filesystem, and would not even let an attacker discern what type of
file-system was in use.
On Fri, Dec 30, 2011 at 14:12, Sandra Schlichting
littlesandr...@gmail.com wrote:
How is this advantageous over dmcrypt-LUKS?
TRIM pass-through for SSD's. With dmcrypt on an SSD write performance
is very slow.
Good point. I'm actually very close to moving from magnetic to SSD
storage for my
Good point. I'm actually very close to moving from magnetic to SSD
storage for my btrfs volumes. Would my luks layer offset the majority
of any advantage I might otherwise see from SSD? I'd be happy just to
eliminate seektime.
Not to my knowledge.
I've been using btrfs on luks now for 6
On Fri, Dec 30, 2011 at 01:27:43PM -0600, Billy Crook wrote:
On Fri, Dec 30, 2011 at 12:32, Sandra Schlichting
littlesandr...@gmail.com wrote:
According to [0] ZFS does encryption:
One exception to this is the encryption support being added to the ZFS
filesystem. Filesystem metadata such
How is this advantageous over dmcrypt-LUKS?
For example mixing encrypted and not encrypted subvolumes in one pool.
And not having to separately cryptsetup luksOpen all disks consisting
filesystem.
There are advantages of FDE like dm-crypt and selective encryption like
in ZFS.
I think
15 matches
Mail list logo
