On 04/07/2015 16:20, Remy Blank wrote:
Yes, they look fine. Maybe try "df -i" on the server side, too? I don't
know if inodes map 1:1 between the NFS server and the client.
ron@D7Gateway:~$ df -i
Filesystem Inodes
IUsed IFree IUse% Mounted on
/dev/mapper/bkp100vg-bkp100lv 173170688
6320288 166850400 4% /mnt/R1/bkp100
ron@D7Gateway:~$
(The word wrap destroyed that, but the report for the LVM indicates 4%
inodes in use.)
Does rdiff-backup create any or many files on / during a run?
I don't think so, but if you want to be sure, run rdiff-backup under strace.
I'll maybe try that.
Thank you very much for the clues, which I think have provided some
evidence for thinking the fs looks ok, with these reports, and with
the static test of a 4GB iso transfer.
I may also try to run a backup with some enhanced logging. I'd
particularly like to see what rdiff-backup calculates the next
increment to be - perhaps it thinks it has 'lost' some tranche of data
and needs to copy or diff it again.
regards, Ron
_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki