Le lun. 18 févr. 2019 à 14:43, Harrison <sainokawara.sisyp...@gmail.com> a écrit : > > Mathieu, > > I am currently using Windows 10 Pro x64 (1511). I plan on upgrading to > (1809) or (1903) in the next month. If it would be help in diagnosing this > problem, I can do it this week. > > What concerns me the most about this problem is that when I use CIFS on the > Debian side, everything works correctly. But, when I use SAMBA from the > Windows side, the "available space" in the root partition is used, instead of > the non-backed partition where the Folder to which I am copying is located, > when I SMB "connect" to root. But, if I SMB "connect" to the Sub-Folder in > the non-backed partition, everything WORKS correctly! The symptoms suggest > to me that the problem is the SAMBA code that initially sets up the copy is > not obtaining the "available space" for the correct partition, non-backed. > > Oh, and just yesterday, an immense number of SAMBA updates appeared and I > installed them. If there was anything in Samba 2:4.5.16+dfsg-1 that might > address this problem, I don't mind testing again. The folders/files that I > am copying in one operation are in the 50-100 GB range. But, there is more > than an adequate amount of "available space" in the partition.
If your share "path" is /mnt (or /), you'll have only 9,6G available. Please send your smb.conf. > Here is the "df -h" output: > > Filesystem Size Used Avail Use% Mounted on > udev 16G 0 16G 0% /dev > tmpfs 3.2G 9.7M 3.2G 1% /run > /dev/mapper/sda3_crypt 59G 9.6G 46G 18% / > tmpfs 16G 0 16G 0% /dev/shm > tmpfs 5.0M 4.0K 5.0M 1% /run/lock > tmpfs 16G 0 16G 0% /sys/fs/cgroup > /dev/sdb1 3.6T 3.1T 333G 91% /mnt/Non-Backed > /dev/sda6 236M 64M 160M 29% /boot > /dev/sda1 487M 132K 486M 1% /boot/efi > /dev/mapper/data 234G 11G 212G 5% /mnt/data > tmpfs 3.2G 16K 3.2G 1% /run/user/116 > tmpfs 3.2G 40K 3.2G 1% /run/user/1000 Regards Mathieu Parent
