Issue with corrent reporting of mnt drive when accessing throug samba

kratax

New Member
Mar 11, 2023
6
0
1
Hi,
I have an issue with a drive connected as lvm-thin, mounted as drive in ubuntu (ext4) and shared via samba. When external host mount this drive through mount.smb3 and uses rsync, there is an erorr after a time:

Code:
pi@raspberrypi:~ $ sudo rsync -aqh --inplace /home/pi/homeassistant /media/ttt/backupha
rsync: [receiver] close failed on "/media/ttt/backupha/homeassistant/backups/6db297dc.tar": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(871) [receiver=3.2.3]
rsync: [sender] write error: Broken pipe (32)

df is showing (last line for connected drive):
Code:
pi@raspberrypi:~ $ sudo df
Filesystem                       1K-blocks               Used           Available Use% Mounted on
/dev/root                        240083840           49606380           180667772  22% /
devtmpfs                           3833708                  0             3833708   0% /dev
tmpfs                              3999436                  0             3999436   0% /dev/shm
tmpfs                              1599776               1520             1598256   1% /run
tmpfs                                 5120                  4                5116   1% /run/lock
/dev/sda1                           258095              53577              204519  21% /boot
tmpfs                               799884                 24              799860   1% /run/user/1000
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/f8403f11845ef035dac5de37f5b51ae185bf660aa6144222bfa59f1c8f839e18/merged
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/e53a01a7b0d5e25742688fa7a40307e9317379646c4029a2dab0ec099cf58dac/merged
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/d6e1c20121876a09bc617c7dd164fb0b4668b450a007b815f5e49d1c49f8c288/merged
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/5b073245cea747a08b7a1e53f57ef4550ee484dba2b7d9c62504875da746b653/merged
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/4a932d15c834fcc87243f7ccc13f5de906e288eabed9622c958326c28f345edf/merged
//10.1.14.24/zaloha/ha 2738188573426692968 936748722478494668 1801439850948198300  35% /media/ttt

Any help with this more than welcomed... second host connected via macos can at the same time write files on the destination without issues...

Just to add, I have added dfree command to samba config, without that, there was really on the connected machine to samba almost no space, although on the destination is 60+% free.. after adding, still error above appears...
 
Last edited:
Hi,
I have an issue with a drive connected as lvm-thin, mounted as drive in ubuntu (ext4) and shared via samba. When external host mount this drive through mount.smb3 and uses rsync, there is an erorr after a time:

Code:
pi@raspberrypi:~ $ sudo rsync -aqh --inplace /home/pi/homeassistant /media/ttt/backupha
rsync: [receiver] close failed on "/media/ttt/backupha/homeassistant/backups/6db297dc.tar": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(871) [receiver=3.2.3]
rsync: [sender] write error: Broken pipe (32)

df is showing (last line for connected drive):
Code:
pi@raspberrypi:~ $ sudo df
Filesystem                       1K-blocks               Used           Available Use% Mounted on
/dev/root                        240083840           49606380           180667772  22% /
devtmpfs                           3833708                  0             3833708   0% /dev
tmpfs                              3999436                  0             3999436   0% /dev/shm
tmpfs                              1599776               1520             1598256   1% /run
tmpfs                                 5120                  4                5116   1% /run/lock
/dev/sda1                           258095              53577              204519  21% /boot
tmpfs                               799884                 24              799860   1% /run/user/1000
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/f8403f11845ef035dac5de37f5b51ae185bf660aa6144222bfa59f1c8f839e18/merged
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/e53a01a7b0d5e25742688fa7a40307e9317379646c4029a2dab0ec099cf58dac/merged
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/d6e1c20121876a09bc617c7dd164fb0b4668b450a007b815f5e49d1c49f8c288/merged
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/5b073245cea747a08b7a1e53f57ef4550ee484dba2b7d9c62504875da746b653/merged
overlay                          240083840           49606380           180667772  22% /var/lib/docker/overlay2/4a932d15c834fcc87243f7ccc13f5de906e288eabed9622c958326c28f345edf/merged
//10.1.14.24/zaloha/ha 2738188573426692968 936748722478494668 1801439850948198300  35% /media/ttt

Any help with this more than welcomed... second host connected via macos can at the same time write files on the destination without issues...

Just to add, I have added dfree command to samba config, without that, there was really on the connected machine to samba almost no space, although on the destination is 60+% free.. after adding, still error above appears...
Sorry, my fault, I found incorrect mounting (outside of shared folder in samba), solved