Page 1 of 1
Incorrect free space on mounted drives inside network share
Posted: 20 Oct 2010, 23:41
by WL
If I'm browsing a network share, Altap Salamander will only show the free space of the root directory. It does not show the free space of the current directory which may be a mounted drive and therefore might have a different amount of free space left. It does work though for mounted drives outside of a network share.
Running AS 2.54 and Windows 7 x64
Re: Incorrect free space on mounted drives inside network sh
Posted: 21 Oct 2010, 15:06
by crystalidea
It's not a bug. Your idea is technically not correct thus impossible.
Re: Incorrect free space on mounted drives inside network sh
Posted: 24 Oct 2010, 01:02
by Ether
@XPiS] It is possible. Say we have a drive W: (123 GiB free) and we mount/junction/symlink a directory from another drive D: (2 GiB free) to W:\temporary. Then if W: is shared as \\computer\W, you can store another 123 GiB into it, but only 2 GiB into \\computer\W\temporary, though the reported free space is still the same.
I *think* I've noticed the same thing at some point, it's just never occured to me that I should report it. But as I tried to reproduce this problem between my Windows 7x64 and Windows7x86, the free space was reported correctly. It leaves me confused. The drives are interconnected by junctions, so is it only happening with mounted drives?
Re: Incorrect free space on mounted drives inside network sh
Posted: 25 Oct 2010, 08:27
by Jan Patera
I believe XPiS meant it is not possible to query the space on the second (sub)share. I am having the same problem: a Mac OS disk mounted to XP over SMB has links to additional disks on the same (Mac) machine. The free space of the first disk is always reported.
I also remember having similar problem that Salamander was ignoring folder quotas on Netware drives (but I no longer have access to Netware).