From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup creates 1.8 Gb when it should be 1Tb
Date: Mon, 28 Oct 2013 16:14:01 -0500 [thread overview]
Message-ID: <l4mk2g$6gl$1@ger.gmane.org> (raw)
In-Reply-To: <20131028202629.GA31940@tansi.org>
On 10/28/2013 03:26 PM, Arno Wagner wrote:
> 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.
I've seen it before in other contexts. Things can get really weird when
there is an ordinary, non-empty file named /dev/null.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
next prev parent reply other threads:[~2013-10-28 21:14 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
2013-10-28 21:14 ` Robert Nichols [this message]
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='l4mk2g$6gl$1@ger.gmane.org' \
--to=rnicholsnospam@comcast.net \
--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.