From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgFNKkn__Nxq for ; Mon, 28 Oct 2013 08:40:42 +0100 (CET) Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Mon, 28 Oct 2013 08:40:42 +0100 (CET) Received: by mail-ea0-f177.google.com with SMTP id f15so1965211eak.36 for ; Mon, 28 Oct 2013 00:40:41 -0700 (PDT) Message-ID: <526E14C2.8060901@gmail.com> Date: Mon, 28 Oct 2013 08:39:46 +0100 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] cryptsetup creates 1.8 Gb when it should be 1Tb List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: metageek , dm-crypt@saout.de On 28.10.2013 3:05, metageek wrote: ... > Then I went on to create the LUKS encryption: > > cryptsetup luksFormat /dev/sdb1 > > then open it: > > cryptsetup luksOpen /dev/sdb1 pjhomecrypt > > now using status to see its properties: > > cryptsetup -v status pjhomecrypt > /dev/mapper/pjhomecrypt is active. > type: LUKS1 > cipher: aes-cbc-essiv:sha256 > keysize: 256 bits > device: /dev/loop0 > loop: /dev/sdb1 ^^^^ Why it is mapped through loop device? Ensure that /dev/sdb1 is BLOCK device. It seems to me that it is in fact just file created by mistake in /dev ... (Then limited by tmpfs size to half of memory or so and explains strange size.) Also use lsblk to verify real kernel sizes (sometimes kernel see old partition size) Milan