From: Phillip Susi <psusi@cfl.rr.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: 2 TB wraparound on 32 bit host
Date: Sat, 12 Jun 2010 13:58:46 -0400 [thread overview]
Message-ID: <4C13CAD6.70902@cfl.rr.com> (raw)
In-Reply-To: <1276358949.4399.8.camel@mulgrave.site>
On 06/12/2010 12:09 PM, James Bottomley wrote:
> Actually, looking at the above, this is conflicting information. On 64
> bit systems (like amd64) there's no need to set CONFIG_LBDAF because
> sector_t is an unsigned long, which is 64 bits. It's only on 32 bit
> configurations it gets set. Initially you said you were using a PAE
> i686 configuration, which would need this setting. An amd64 one
> wouldn't.
>
> Which kernel are you actually seeing the problem on, and what is
> CONFIG_LBDAF set to on that kernel?
I am seeing the wraparound on two systems, one running the vanilla i386
Ubuntu Karmic kernel, and one running amd64 Lucid. I checked the config
file on the amd64 system I am on now and the symbol CONFIG_LBDAF is not
there. I just checked the i386 config and it is set there. It seems
then, that this is not the cause of the problem after all.
next prev parent reply other threads:[~2010-06-12 17:58 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
2010-06-12 16:03 ` James Bottomley
2010-06-12 16:09 ` James Bottomley
2010-06-12 17:58 ` Phillip Susi [this message]
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=4C13CAD6.70902@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=James.Bottomley@HansenPartnership.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.