All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup creates 1.8 Gb when it should be 1Tb
Date: Mon, 28 Oct 2013 21:26:29 +0100	[thread overview]
Message-ID: <20131028202629.GA31940@tansi.org> (raw)
In-Reply-To: <loom.20131028T201307-11@post.gmane.org>

Interesting. This one was new for me.

Arno

On Mon, Oct 28, 2013 at 20:28:31 CET, metageek wrote:
> Ok, problem solved now,
> 
> the last poster was spot on, for some reason that I cannot figure out, there
> was a regular file /dev/sdb1. After removing it (with the drive
> disconnected), everything works. 
> 
> The drive is a Seagate Backup Plus portable drive
>  
> I'm running cryptsetup version 1.4.3 (the version in Slackware64 14.0,
> running kernel 3.8.8)
> 
> # dd if=/dev/zero of=/dev/sdb bs=1GB
> dd: writing '/dev/sdb': No space left on device
> 1001+0 records in
> 1000+0 records out
> 1000204885504 bytes (1.0 TB) copied, 12064.5 s, 82.9 MB/s
> 
> so it is really 1.0 TB there (not a fake one)
> 
> #smartctl -i
> /dev/sdb: Unknown USB bridge [0x0bc2:0xa013 (0x100)]
> 
> Now, status reports the full drive and no loopback:
> 
> # cryptsetup -v status pjhomecrypt
> /dev/mapper/pjhomecrypt is active.
>   type:    LUKS1
>   cipher:  aes-cbc-essiv:sha256
>   keysize: 256 bits
>   device:  /dev/sdb1
>   offset:  4096 sectors
>   size:    1953521008 sectors
>   mode:    read/write
> Command successful.
> 
> The filesystem was created successfully with ~ 1 TB.
> 
> Problem solved.
> Thanks everyone!
> 
> 
> 
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult.  --Tony Hoare

  reply	other threads:[~2013-10-28 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28  2:05 [dm-crypt] cryptsetup creates 1.8 Gb when it should be 1Tb metageek
2013-10-28  2:54 ` Arno Wagner
2013-10-28  3:30 ` David Christensen
2013-10-28  7:39 ` Milan Broz
2013-10-28 19:28   ` metageek
2013-10-28 20:26     ` Arno Wagner [this message]
2013-10-28 21:14       ` Robert Nichols
2013-10-29  0:19         ` Arno Wagner
2013-10-28 20:42     ` David Christensen

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=20131028202629.GA31940@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.