lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: linux (Ubuntu Lucid)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
** Changed in: linux (Ubuntu Lucid)
Status: New = Triaged
** Changed in: linux (Ubuntu Lucid)
Importance: Undecided = High
--
You
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/593086
Title:
Silent wraparound on 2 TB LVM snapshots in lucid and karmic
--
ubuntu-bugs mailing list
Now that I look at it again, it looks like this only affects snapshots.
** Summary changed:
- Silent wraparound on 2 TB LVM volumes in lucid
+ Silent wraparound on 2 TB LVM snapshots in lucid and karmic
--
Silent wraparound on 2 TB LVM snapshots in lucid and karmic
Thanks for your testing Phillip. My apologies for the script bug that
hit you. We are fixing that now.
~JFo
--
Silent wraparound on 2 TB LVM snapshots
https://bugs.launchpad.net/bugs/593086
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
After discussing it on dm-de...@redhat.com, I believe the issue has been
found. There was a patch in 2.6.32 that caused this breakage, and was
later fixed. The broken patch ended up in Ubuntu Lucid and Karmic
kernels. This probably should be corrected with an SRU. From the
mailing list
** Changed in: linux (Ubuntu)
Milestone: None = lucid-updates
** Changed in: linux (Ubuntu)
Milestone: lucid-updates = karmic-updates
** Changed in: linux (Ubuntu)
Milestone: karmic-updates = None
** Description changed:
Ubuntu kernels silently wrap access to disk locations above
** Description changed:
Ubuntu kernels silently wrap access to disk locations above 2 TB back
around to zero. This can easily be reproduced using lvm to create a
thin provisioned virtual disk:
lvcreate -s -n thin -L 1g --virtualsize 3t vg0
mke2fs -t ext4 -E lazy_itable_init
It looks like it was fixed in mainline between 2.6.32 and 2.6.33. I can
find no commits that sound intended to fix this, but there were a number
of changes to the snapshot code, so I guess one of them inadvertently
fixed this.
--
Silent wraparound on 2 TB LVM snapshots
Hi Phillip,
Please be sure to confirm this issue exists with the latest development release
of Ubuntu. ISO CD images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please
run the following command from a Terminal
(Applications-Accessories-Terminal).
This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested
apport information
** Tags added: apport-collected
** Description changed:
Ubuntu kernels silently wrap access to disk locations above 2 TB back
around to zero. This can easily be reproduced using lvm to create a
thin provisioned virtual disk:
lvcreate -s -n thin -L 1g --virtualsize
Quite some time? It's been 13 hours man... testing upstream kernel
now...
** Changed in: linux (Ubuntu)
Status: Expired = Incomplete
** Tags removed: apport-collected kj-expired
--
Silent wraparound on 2 TB LVM snapshots
https://bugs.launchpad.net/bugs/593086
You received this bug
linux-image-2.6.35-999-generic_2.6.35-999.20100653_amd64.deb does
not seem to have this problem.
** Tags added: apport-collected
--
Silent wraparound on 2 TB LVM snapshots
https://bugs.launchpad.net/bugs/593086
You received this bug notification because you are a member of Ubuntu
Bugs,
2.6.35-2 currently in use on maverick also does not appear to have the
problem.
--
Silent wraparound on 2 TB LVM snapshots
https://bugs.launchpad.net/bugs/593086
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Also tested linux-image-2.6.32-020632-generic_2.6.32-020632_amd64.deb,
which was the closest mainline build I could see to the 2.6.32-22 build
lucid is using, and it is also affected, so it looks like this was an
upstream bug that got fixed somewhere between 2.6.32 and 2.6.35.
--
Silent
2.6.33 also is unaffected.
--
Silent wraparound on 2 TB LVM snapshots
https://bugs.launchpad.net/bugs/593086
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Narrowed it down to lvm snapshots. Using dmsetup to create a linear
mapping greater than 2tb has no problem reading and writing over the 2tb
mark correctly, so it appears that the problem is in dm-snapshot.
** Summary changed:
- Silent wraparound on 2 TB disks
+ Silent wraparound on 2 TB LVM
** Description changed:
Ubuntu kernels silently wrap access to disk locations above 2 TB back
around to zero. This can easily be reproduced using lvm to create a
thin provisioned virtual disk:
- lvcreate --type zero -L 3t -n empty vg0
- lvcreate -s -n thin vg0/zero -L 1g
+ lvcreate -s
19 matches
Mail list logo
