I am trying to understand why the backup process in one of the servers is taking so long and not copying the data correctly.
This is the size of the external HDD partition.
df -h /dev/sdb1
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 985G 362G 573G 39% /media/backup
The folder that I am trying to copy is lesser than the size of the external HDD partition.
df -h /dev/sda4
Filesystem Size Used Avail Use% Mounted on
/dev/sda4 3.4T 867G 2.4T 27% /mounts
Everything just seemed fine. I started the backup process almost a week back and still it has not completed. I realized it might be an issue with the USB port speed but I was wrong.
I also suspected it might be a corrupted file system that might be causing the error. I wanted to run fsck
on the /dev/sda4
file system. But when I checked some of the script output, I read some error messages as,
rsync: mkstemp "/media/backup/2014-06-18_09-36/mounts/ no space left on device (28)
From here, I read that 5% of the disk space would be allocated for root file system. I do not understand if that is related to my problem. Also, from here, I read the inode size cannot be greater than 2 GB. I believe it should be something that I investigate. But am not sure if that is the problem though. I would appreciate more pointers towards the right direction.
EDIT:
The output of df -i
command is as below.
df -i /dev/sdb1
/dev/sdb1 65544192 65279823 264369 100% /media/backup
df -i /dev/sda4
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda4 229957632 171244050 58713582 75% /mounts
df -i
? Also, what filesystem is used on the external drive? – derobert Jun 24 '14 at 16:02df -i
command output. It seems promising. Does it mean something? – Ramesh Jun 24 '14 at 16:05rsync
usesmkstemp()
for, but to guess, probably so that it doesn't create partial files on error. Running out of inodes does seem like a likely cause. – goldilocks Jun 24 '14 at 16:06