When exposing an archivemount-ed directory over samba the directory is inaccessible from Windows client

As the title says, the archivemounted directory is displayed as a file through samba, so it cannot be accessed. From my searching this may be because the hardlink count is displayed as 0 instead of 2.

[braian87b]

Any news on this ?...
The informed size by ls -lath . shows the archive size instead of the usual 4k directory size allocation, may be is because of that?

The mount point is shown as a file of 0 bytes in samba share...

Tryed -o allow_other
Tryed -o umask=0
Tryed with symbolic link ln -s /mnt/archive/directory /mnt/archive2.

[bramp]

I'm sorry, I have not looked at this, and nor do I have a Windows machine to test with.

[braian87b]

No need to test in windows, it happens the same on macOS and Debian...

I actually tried to test something similar with a .zip file using fuse-zip and it works...

It seems to be the method used to present the volume to the system.

On samba share "./archive" appears as a file of 0 bytes, and file could not be accessed.

#with fuse-zip, Works just fine and can browse files and directories on samba share.
root@backups:/home/user# stat /mnt/archive/
  File: ‘/mnt/archive/’
  Size: 0         	Blocks: 0          IO Block: 512    directory
Device: 24h/36d	Inode: 1           Links: 3
Access: (0775/drwxrwxr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2017-06-12 19:33:49.000000000 -0300
Modify: 2017-06-12 19:33:49.000000000 -0300
Change: 2017-06-12 19:33:49.000000000 -0300
 Birth: -

#with archivemount:

root@backups:/home/user# archivemount -o readonly /mnt/combine/backup.tar.gz.000.raw /mnt/archive
root@backups:/home/user# archivemount -o readonly,allow_other /mnt/combine/backup.tar.gz.000.raw /mnt/archive
root@backups:/home/user# archivemount -o readonly,allow_other,default_permissions /mnt/combine/backup.tar.gz.000.raw /mnt/archive
root@backups:/home/user# stat /mnt/archive/
  File: ‘/mnt/archive/’
  Size: 1453919738	Blocks: 2839687    IO Block: 4096   directory
Device: 24h/36d	Inode: 1           Links: 0
Access: (0555/dr-xr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 1969-12-31 21:00:00.000000000 -0300
Modify: 1969-12-31 21:00:00.000000000 -0300
Change: 1969-12-31 21:00:00.000000000 -0300
 Birth: -

# with umask=0 changes Access to 0777, but problem persist
root@backups:/home/user# archivemount -o readonly,allow_other,umask=0 /mnt/combine/backup.tar.gz.000.raw /mnt/archive
root@backups:/home/user# stat /mnt/archive/
...
Access: (0777/drwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
...
root@backups:/home/user# chmod 777 /mnt/archive/
chmod: changing permissions of ‘/mnt/archive/’: Read-only file system

root@backups:/home/user# uname -a
Linux backups 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2 (2017-04-30) x86_64 GNU/Linux

root@backups:/home/user# cat /proc/version
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.43-2 (2017-04-30)

root@backups:/home/user# cat /etc/debian_version
8.8

[braian87b]

Please change issue Title to "The mount point is shown as a file of 0 bytes on Samba share..."

I connected to share using Windows, Debian and macOS and behaviour is the same always.

Please let me know if you have an idea about this, I will try to test it asap. Thanks!

[Darkvater]

I have the same. Really thought this would be transparent as it's a fuser mount?