GNOME Bugzilla – Bug 550684
Nautilus can't correctly find the available disk space when dealing with mounted samba shared directory
Last modified: 2016-11-11 17:18:39 UTC
Please describe the problem: A remote file system directory of size 284Gig is shared using samba and mounted on a local file system directory /home/foo/Backup which is of size 14Gigs. When a file of 15.2Gigs is tried to be copied to the remote file system directory through the locally mounted directory, nautilus reports an Error that there is not enough space to copy a 15.2G file on to a 14G directory though it is actually represents a 284G directory on the remote file system. Steps to reproduce: 1. Share a large file system (directory) on a remote machine using samba 2. Mount the shared file system on to a local file system directory smaller than the remote file system (directory) being shared 3. Copy a file larger than the size of the local mount directory but which can be accommodated in the remote file system (directory) Actual results: Nautilus displays an error dialog that the target directory for copying the file is smaller than the size of the file. Also the size of the target directory is not the size of the remote file system, which should be so as it is the mount point of the remote file system. Expected results: As the local target directory for copying the file is actually a remote file system mount, where the remote file system has enough space to accommodate the file being copied, it should be copied to the remote file system without any problem. Nautilus should also display the size of the target directory as that of the remote file system as it is a mount of the remote file system Does this happen every time? Yes Other information: The bug was reported in Launchpad at https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/243431 and was suggested to report it upstream.
Thanks for the bug report! * How did you mount the file system? * Maybe you could check the following: try “gvfs-info -f .” in the root of the mounted file system try “gvfs-info -f .” in the parent directory of the mount point
Ah, now I see. Your launchpad bug report is very verbose: https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/243431 You have multiple server-side mounts inside the share, and only the share's size is considered if you want to move something into the remote mount point. There is at least one Nautilus issue involved (which you are probably NOT seeing): We just add up the overall required size, and check whether that space is available on the top-level destination directory, while in fact - when moving entire hierarchies - they may perfectly be merged with mount points. This scenario is somewhat rarely seen, but a button to force a file operation even though not enough space is available may be a good idea. Then there may be another issue (which you are probably experiencing): It may be the case that the mount mechanism used to mount the remote share is not aware of remote mount points, and does not propagate the actual mount's free file system capacity. Please post the output of gvfs-info -f foo ^^ top-level samba mount directory gvfs-info -f foo/disk ^^ nested remote mount, proxied through samba on the *client side*. On the server side, this should of course give the correct sizes anway (maybe you could check it as well).
Closing as required info has not been provided in 8 years.