From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: 2 TB wraparound on 32 bit host
Date: Fri, 11 Jun 2010 16:57:16 -0400 [thread overview]
Message-ID: <4C12A32C.3000501@cfl.rr.com> (raw)
I am seeing access to > 2tb on a dm target silently wrap around to 0.
Simple recreation steps:
lvcreate --type zero -L 3TB -n empty vg0
lvcreate -s vg0/empty -L 10G -n thin
mke2fs -t ext4 -E lazy_itable_init /dev/vg0/thin
e2fsck -f /dev/vg0/thin
The fsck will find block bitmap differences on a cleanly formatted fs
that seem to be caused by wraparound. Accessing block 536870912 with dd
seems to return the superblock instead of the block allocation bitmap
that should be located there.
This is using kernel 2.6.31-21-generic-pae i686 build from Ubuntu 9.10.
Is this a known issue and/or can anyone reproduce it?
next reply other threads:[~2010-06-11 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 20:57 Phillip Susi [this message]
2010-06-11 21:16 ` 2 TB wraparound on 32 bit host 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
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=4C12A32C.3000501@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.