All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: 2 TB wraparound on 32 bit host
Date: Sat, 12 Jun 2010 11:45:20 -0400	[thread overview]
Message-ID: <4C13AB90.1070802@cfl.rr.com> (raw)
In-Reply-To: <1276290990.2862.161.camel@mulgrave.site>

On 06/11/2010 05:16 PM, James Bottomley wrote:
> So best guess is that CONFIG_LBDAF isn't set.  This would make all
> sector_t counts wrap at 2TB (32 bits worth of 512 bytes).  It would be
> rather a daft thing for a distribution not to have set, though ...

Bingo, thanks.  It doesn't seem to be set on this machine running the 
amd64 2.6.32 lucid build which also appears to suffer the same problem. 
  If this config option isn't set though, shouldn't the kernel fail 
calls like llseek() that try to exceed the limit, rather than silently 
wrap around to the wrong address?

  reply	other threads:[~2010-06-12 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 20:57 2 TB wraparound on 32 bit host Phillip Susi
2010-06-11 21:16 ` James Bottomley
2010-06-12 15:45   ` Phillip Susi [this message]
2010-06-12 16:03     ` James Bottomley
2010-06-12 16:09       ` James Bottomley
2010-06-12 17:58         ` Phillip Susi
2010-06-12 18:47           ` 2 TB wraparound on snapshots Phillip Susi
2010-06-12 20:03             ` James Bottomley
2010-06-12 22:03               ` Phillip Susi
2010-06-15 14:57                 ` 2 TB wraparound on snapshots on kernels < 2.6.33 Phillip Susi
2010-06-16 13:13                   ` Mikulas Patocka
2010-06-16 13:45                     ` Mikulas Patocka
2010-06-16 13:52                       ` Phillip Susi

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=4C13AB90.1070802@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=dm-devel@redhat.com \
    /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.