Update: unionfs 1.1.2 -> 1.1.5

Bug #50328 reported by Martin Kreiner
4
Affects Status Importance Assigned to Milestone
unionfs (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Would be nice to have have it updated.

Unionfs Mailinglist:

Unionfs 1.1.5 has just been released. This release includes a bunch of
fixes back-ported from the 1.2 branch. This release is meant to fix up some
major issues from version 1.1.4 only, and is intended for 2.6.9 - 2.6.15
kernels. With newer kernels you must use version 1.2 or a CVS snapshot.

The package can be found at
ftp://ftp.fsl.cs.sunysb.edu/pub/unionfs/unionfs-1.1.5.tar.gz

* Unionfs 1.1.5
- Backport: Corrected sample mount commands
- Backport: Fixed link-unlink issue
- Backport: Fixed ref-counting leak (if a branch doesn't exist during mount,
  the previously looked up branches were not freed properly)
- Backport: Fixed inode_permission returning EROFS when it wasn't supposed
  to
- Backport: Fixed bug #501 (mv dir ..)

Unionfs 1.1.4 has just been released. This release includes a bunch of
fixes backported from the 1.2.x branch. This release is ment to fix up
some major issues from version 1.1.3 only.

The package can be found at
ftp://ftp.fsl.cs.sunysb.edu/pub/unionfs/unionfs-1.1.4.tar.gz

* Unionfs 1.1.4
- Backport: On error, NULL the pointers after free - Fixes nasty mount
  bug
- Backport: Fixed unionfs_permission on reiserfs and XFS
- Backport: Added check to see if its necessary to run the delete_all
  regression tests
- Added explicit check for kernel versions newer than 2.6.15
(If you want to use 2.6.16 or newer, look at Unionfs 1.2.x)

Unionfs 1.1.3 has just been released. This release includes a bunch of fixes and some code cleanup. After this version we will be increasing the minimum kernel version for Unionfs to 2.6.16 and will attempt to closely track the latest and greatest kernels (with an eye towards submitting it for inclusion).

The package can be found at
ftp://ftp.fsl.cs.sunysb.edu/pub/unionfs/unionfs-1.1.3.tar.gz

* Unionfs 1.1.3
- Simplified delete=whiteout
- Switched default delete mode to the simpler whiteout mode
- Disable delete=all by default (enable with -DUNIONFS_DELETE_ALL)
- Removed all copy up modes except preserve (the old default)
- Unlink partially copied up files
- Compartmentalize malloc debugging
- Fix uid/gid/mode not being reset when a whiteout is recreated
- Fix stale atime/mtime bugs for recreated whiteouts
- Cleaned up persistent inode code a bit (still unstable)

Revision history for this message
Motin (motin) wrote :

Thanks for the bug report. I'm closing it because the bug has been fixed in Feisty (the version of unionfs packages are now 1.4 - even Edgy had 1.3). It won't be fixed in 6.06 because the bug doesn't fit requirements for backporting. See <https://wiki.ubuntu.com/UbuntuBackports> for more information.

Changed in linux-source-2.6.15:
status: Unconfirmed → Fix Released
Revision history for this message
C. Scott Ananian (cscott-litl) wrote :

Upgrading unionfs to the version with delete=whiteout has the side effect that unionfs-mounted filesystems (like in ubuntu live images) eventually fill up the rw partition with whiteout files, run out of inodes, and crash. It is probably worth enabling delete=all and making it the Ubuntu default. See lp bug 435492 for more information.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.