Public bug reported:
Binary package hint: unionfs-fuse
Unionfs-fuse does strange things when I tell it to create a union of two
directories, and I specify them via relative pathnames. I look into
the resulting directory and I see the root filesystem.
To recreate the problem:
$ cd $HOME
$ mkdir foo bar gleep
$ echo one >foo/one
$ echo two >bar/two
$ unionfs-fuse -o cow foo=RW:bar=RO gleep
$ ls gleep
bin etc lib media root sys vmlinuz
boot home lib32 mnt sbin tmp vmlinuz.old
cdrom initrd.img lib64 opt selinux usr xorg.conf.new
dev initrd.img.old lost+found proc srv var
$
Of course, what we expected to see was "one" and "two".
You can get that by using absolute pathnames:
$ fusermount -u gleep
$ unionfs-fuse -o cow $HOME/foo=RW:$HOME/bar=RO gleep
$ ls gleep
one two
$
These two invocations should be equivalent. Therefore, there is a
bug in the way unionfs-fuse handles relative pathnames.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: unionfs-fuse 0.23.hg.20090611-1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Dec 14 19:58:44 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: unionfs-fuse
** Affects: unionfs-fuse (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690348
Title:
Unexpected behavior when given relative pathnames.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
