From: Felix Blanke <felixblanke@gmail.com>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Bug in mkfs.btrfs?!
Date: Mon, 24 Jan 2011 10:38:35 +0100 [thread overview]
Message-ID: <20110124093835.GA24477@scooter> (raw)
In-Reply-To: <AANLkTimXNxakkozObyZCDK+sJqNU5edJrY4ywgERdELC@mail.gmail.com>
Counter question: Why should I? :)
I used dm-crypt with luks some time ago, but it is really slooow. So I =
talked with
the dm-crypt devs. and they gave me the hint to test loop-aes, for more=
speed. It is
about 4x faster for me :)
And I don't see any advantages using dm-crypt instead of loop-aes.
=46elix
On 24. January 2011 - 08:53, Fajar A. Nugraha wrote:
> Date: Mon, 24 Jan 2011 08:53:41 +0700
> From: "Fajar A. Nugraha" <list@fajar.net>
> To: Felix Blanke <felixblanke@gmail.com>
> Cc: linux-btrfs@vger.kernel.org
> Subject: Re: Bug in mkfs.btrfs?!
>=20
> On Mon, Jan 24, 2011 at 6:58 AM, Felix Blanke <felixblanke@gmail.com>=
wrote:
> > I tried the newest version 2.19-rc1. There seems to be some kind of=
"fix":
> >
> > scooter ~ # /home/fame/tmp/util-linux-2.19-rc1/mount/losetup -a
> > /dev/loop0: [0010]:3154
> > (/dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO939201JX160AGN-pa*), =
encryption =A0(type
> > 16)
>=20
> > If the path is to long they add a '*' :) Do you think that will sol=
ve the problem?
>=20
> It shouldn't.
>=20
> However, since you're using loopback for encryption, why not use
> dm-crypt instead?
>=20
> --=20
> Fajar
---end quoted text---
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-24 9:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 14:45 Bug in mkfs.btrfs?! Felix Blanke
2011-01-22 14:52 ` Felix Blanke
2011-01-22 15:11 ` Hugo Mills
2011-01-22 15:45 ` Hugo Mills
2011-01-22 15:56 ` Felix Blanke
2011-01-22 22:54 ` Chris Samuel
2011-01-22 23:03 ` Felix Blanke
2011-01-23 18:18 ` Hugo Mills
2011-01-23 22:02 ` Goffredo Baroncelli
2011-01-23 23:15 ` Felix Blanke
2011-01-24 7:42 ` Helmut Hullen
2011-01-24 9:41 ` Felix Blanke
2011-01-23 23:27 ` Hugo Mills
2011-01-23 23:58 ` Felix Blanke
2011-01-24 1:53 ` Fajar A. Nugraha
2011-01-24 9:38 ` Felix Blanke [this message]
2011-01-24 13:01 ` Felix Blanke
2011-01-24 13:13 ` Hugo Mills
2011-01-24 13:53 ` Felix Blanke
2011-01-24 14:29 ` Hugo Mills
2011-01-24 14:34 ` Hugo Mills
2011-01-24 14:44 ` Felix Blanke
2011-01-24 16:52 ` Felix Blanke
2011-01-24 17:00 ` Hugo Mills
2011-01-24 21:04 ` Felix Blanke
2011-01-24 21:14 ` Felix Blanke
2011-01-24 14:35 ` Felix Blanke
2011-01-25 0:15 ` LOOP_GET_STATUS(64) truncates pathnames to 64 chars (was Re: Bug in mkfs.btrfs?!) Chris Samuel
2011-02-10 12:29 ` Petr Uzel
2011-02-11 13:04 ` Felix Blanke
2011-02-11 18:59 ` Milan Broz
[not found] ` <AANLkTi=Arg-09F0DXsWNhsYgyPar=rKs7G_OQG2uMm4f@mail.gmail.com>
2011-02-11 19:31 ` Milan Broz
2011-02-11 19:41 ` Felix Blanke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110124093835.GA24477@scooter \
--to=felixblanke@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).