← Back to team overview

kernel-packages team mailing list archive

[Bug 593086] Re: Silent wraparound on > 2 TB LVM snapshots in lucid and karmic

 

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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/593086

Title:
  Silent wraparound on > 2 TB LVM snapshots in lucid and karmic

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Won't Fix

Bug description:
  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 /dev/vg0/thin
  e2fsck -f /dev/vg0/thin

  Fsck will find errors in the bitmap because it is actually reading the
  superblock instead of the allocation bitmap situated just after the 2
  tb mark.

  This affects Karmic and Lucid and will cause data loss and severe
  filesystem corruption that may go unnoticed for some time, if someone
  creates a snapshot of a 2TB + size logical volume.  It was fixed
  upstream as of 2.6.33.

  See comment #26 for details on the problem and what needs done to fix
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/593086/+subscriptions