archivemount reports wrong directory structure when subdir has the same name as its parent dir
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
archivemount (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Running Linux Mint 16 Cinnamon 64-bit
Test case:
==========
$ archivemount --version
archivemount version 0.8.1
FUSE library version: 2.9.2
fusermount version: 2.9.2
using FUSE kernel interface version 7.19
$ mkdir -p test/test mount
$ touch test/a test/test/b
$ tar -c test -f test.tar
$ archivemount test.tar mount
fuse: missing mountpoint parameter
Actual result:
==============
The file test/test/b is reported to be in test instead, but is accessible under neither path:
$ ls -R mount
mount:
test
mount/test:
ls: cannot access mount/test/b: No such file or directory
a b test
mount/test/test:
$ ls mount/test/b
ls: cannot access mount/test/b: No such file or directory
$ ls mount/test/test/b
ls: cannot access mount/test/test/b: No such file or directory
Expected result:
================
A file named b should be accessible under mount/test/test, like so:
$ ls -R mount
mount:
test
mount/test:
a test
mount/test/test:
b
$ ls mount/test/b
ls: cannot access mount/test/b: No such file or directory
$ ls mount/test/test/b
b
Reproducibility: Always
This behavior does not appear if test/test is instead named test/something_
The "fuse: missing mountpoint parameter" message seems to be always displayed if archivemount completes successfully, as a quick google search shows, so I guess it is an unrelated issue?
affects: | linuxmint → archivemount (Ubuntu) |
Status changed to 'Confirmed' because the bug affects multiple users.