From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: 2 TB wraparound on snapshots
Date: Sat, 12 Jun 2010 18:03:39 -0400 [thread overview]
Message-ID: <4C14043B.7080203@cfl.rr.com> (raw)
In-Reply-To: <1276373001.4399.11.camel@mulgrave.site>
On 06/12/2010 04:03 PM, James Bottomley wrote:
> So do you have a 64 bit system (like an amd64) that you can try this
> with? If it only occurs on the i686 system, then it's likely a long to
> sector conversion bug somewhere in the snapshot code. If it occurs on
> both, there's some 2TB limit coded directly into snapshots.
As I said before, it occurs on both.
next prev parent reply other threads:[~2010-06-12 22:03 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
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 [this message]
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=4C14043B.7080203@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.