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] btrfs and "requested offset is beyond real size of device"
Date: Mon, 16 Feb 2015 08:24:26 +0100	[thread overview]
Message-ID: <20150216072426.GA9383@tansi.org> (raw)
In-Reply-To: <CANvLvzALpr-s1S4D+vAf7UdAyxcO2n3E+Hg9HgjesSh4aioV4w@mail.gmail.com>

Just one data-point: LUKS does not store device size. It gets 
queried on mapping. What it stores is the data-offset, i.e.
where the data-area starts after they keyslot-area.

Can you reproduce this with strace and a password that is not 
secret? ("strace cryptsetup ...") That should tell us in which 
call the error happens.

Arno 

On Sun, Feb 15, 2015 at 23:43:22 CET, Jay Sullivan wrote:
> Hi,
> 
> I don't know if this belongs on the btrfs, GRUB, or LUKS mailing list, but
> it is a cryptsetup error, so I figure maybe someone here can help me
> understand what this error means.
> 
> *What I'm doing*
> 
> I'm trying to set up a system with a btrfs /boot partition, and a few
> encrypted btrfs-over-LUKS partitions. Nothing special, except that I'm
> using btrfs for all of my partitions.
> 
> *The Problem*
> 
> I did get the setup "working", I'm able to successfully boot into it.
> Here's the weird part: it only successfully boots about half of the time.
> 
> The other half of the time,  I see this error just after I successfully
> enter my password:
> 
>     requested offset is beyond real size of device
> 
> When this happens, it continues to fail when it prompts me again for my
> password, until I reboot.  It seems to fall into this issue about 50% of
> the boots.
> 
> The culprit seems to be when the /boot partition is btrfs. If I use ext4 as
> /boot, everything works fine and dandy.
> 
> This should be reproducible on any machine, I've tried several times on
> different machines to rule out hardware. I can give complete instructions
> to reproduce if someone wants it, but before I go through the effort, has
> anyone heard of this behavior before? Does anyone have any insight on why
> this may be happening, especially why it only happens sometimes.
> 
> I'm using Ubuntu 14.10's LiveCD to install the operating system, where
> cryptsetup's version says 1.6.1, and btrfs's version is 3.14.1.
> 
> Thanks,
> Jay Sullivan

> _______________________________________________
> 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
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2015-02-16  7:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 22:43 [dm-crypt] btrfs and "requested offset is beyond real size of device" Jay Sullivan
2015-02-16  7:24 ` Arno Wagner [this message]
2015-02-16  8:31 ` Milan Broz
2015-02-16 21:28   ` Jay Sullivan
2015-02-17 13:14     ` Arno Wagner

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=20150216072426.GA9383@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.