unionfs-fuse does check for file existence lower level mounts first
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unionfs-fuse (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: unionfs-fuse
Install sshfs, unionfs-fuse
Then do:
sshfs -o uid=1000,
unionfs-fuse -o cow,use_ino /local/
su - user
startkde
starting of KDE will be extremely slow if sshfs is mounted. If you do not mount sshfs, but have the unionfs-fuse-mount done, startkde will be fast.
I could find unionfs accessing all inodes on all fs first (ascending from /remote/user to /local/user), instead of only accessing the first given (/local/user) if the file could be found there. Descending only if the file could not be found.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: unionfs-fuse 0.23.hg.20090611-1
Uname: Linux 2.6.35.9 x86_64
Architecture: amd64
Date: Thu Dec 30 12:36:47 2010
ProcEnviron:
PATH=(custom, user)
LANG=de_DE.utf8
SHELL=/bin/bash
SourcePackage: unionfs-fuse
| Thomas Schweikle (tps) wrote | #1 |
| Thomas Schweikle (tps) wrote | #2 |
| Thomas Schweikle (tps) wrote | #3 |
sshfs does not crop well with concurrent reads and writes. It works OK with "Walky-Talky" like access. This is an old problem, never addressed. AFAIK it isn't even addressable.