[Kernel-packages] [Bug 1724165] Re: receive_freeobjects() skips freeing some objects

2018-06-29 Thread Launchpad Bug Tracker
[Expired for zfs-linux (Ubuntu) because there has been no activity for
60 days.]

** Changed in: zfs-linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1724165

Title:
  receive_freeobjects() skips freeing some objects

Status in zfs-linux package in Ubuntu:
  Expired

Bug description:
  When receiving a FREEOBJECTS record, receive_freeobjects()
  incorrectly skips a freed object in some cases. Specifically, this
  happens when the first object in the range to be freed doesn't exist,
  but the second object does. This leaves an object allocated on disk
  on the receiving side which is unallocated on the sending side, which
  may cause receiving subsequent incremental streams to fail.

  The bug was caused by an incorrect increment of the object index
  variable when current object being freed doesn't exist.  The
  increment is incorrect because incrementing the object index is
  handled by a call to dmu_object_next() in the increment portion of
  the for loop statement.

  Affects ZFS send.
  Upstream fix
  
https://github.com/zfsonlinux/zfs/pull/6695/commits/d79b4b3e4ad722bf457efe9401d7f267a8dfcc6c

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1724165] Re: receive_freeobjects() skips freeing some objects

2018-04-30 Thread Colin Ian King
** Changed in: zfs-linux (Ubuntu)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1724165

Title:
  receive_freeobjects() skips freeing some objects

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  When receiving a FREEOBJECTS record, receive_freeobjects()
  incorrectly skips a freed object in some cases. Specifically, this
  happens when the first object in the range to be freed doesn't exist,
  but the second object does. This leaves an object allocated on disk
  on the receiving side which is unallocated on the sending side, which
  may cause receiving subsequent incremental streams to fail.

  The bug was caused by an incorrect increment of the object index
  variable when current object being freed doesn't exist.  The
  increment is incorrect because incrementing the object index is
  handled by a call to dmu_object_next() in the increment portion of
  the for loop statement.

  Affects ZFS send.
  Upstream fix
  
https://github.com/zfsonlinux/zfs/pull/6695/commits/d79b4b3e4ad722bf457efe9401d7f267a8dfcc6c

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1724165] Re: receive_freeobjects() skips freeing some objects

2018-03-29 Thread Colin Ian King
** Changed in: zfs-linux (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1724165

Title:
  receive_freeobjects() skips freeing some objects

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  When receiving a FREEOBJECTS record, receive_freeobjects()
  incorrectly skips a freed object in some cases. Specifically, this
  happens when the first object in the range to be freed doesn't exist,
  but the second object does. This leaves an object allocated on disk
  on the receiving side which is unallocated on the sending side, which
  may cause receiving subsequent incremental streams to fail.

  The bug was caused by an incorrect increment of the object index
  variable when current object being freed doesn't exist.  The
  increment is incorrect because incrementing the object index is
  handled by a call to dmu_object_next() in the increment portion of
  the for loop statement.

  Affects ZFS send.
  Upstream fix
  
https://github.com/zfsonlinux/zfs/pull/6695/commits/d79b4b3e4ad722bf457efe9401d7f267a8dfcc6c

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1724165] Re: receive_freeobjects() skips freeing some objects

2018-03-12 Thread Colin Ian King
Do you mind identifying which kernel and release you are using.

** Changed in: zfs-linux (Ubuntu)
   Status: New => Triaged

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1724165

Title:
  receive_freeobjects() skips freeing some objects

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  When receiving a FREEOBJECTS record, receive_freeobjects()
  incorrectly skips a freed object in some cases. Specifically, this
  happens when the first object in the range to be freed doesn't exist,
  but the second object does. This leaves an object allocated on disk
  on the receiving side which is unallocated on the sending side, which
  may cause receiving subsequent incremental streams to fail.

  The bug was caused by an incorrect increment of the object index
  variable when current object being freed doesn't exist.  The
  increment is incorrect because incrementing the object index is
  handled by a call to dmu_object_next() in the increment portion of
  the for loop statement.

  Affects ZFS send.
  Upstream fix
  
https://github.com/zfsonlinux/zfs/pull/6695/commits/d79b4b3e4ad722bf457efe9401d7f267a8dfcc6c

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp