rsync file limit

A 5 star hangout for overworked and underpaid system admins.
Post Reply
JimL
Posts: 2
Joined: 2019/03/06 19:05:42

rsync file limit

Post by JimL » 2019/03/06 20:08:28

Many of our customers still run servers on CentOS 5.11 and use rsync 3.0.6 to synchronize bmp signature picture files from their hard drive to a flash drive for backup purposes. However, I discovered that a maximum of only 32,765 files are written to the sigcaps directory on the flash drive. The rsync command is:

rsync -a /keypos/sigcaps/ /mnt/usbdrive/sigcaps/

Apparently, once the 32765 file count is reached, it starts producing errors like this sample even though there's plenty of space left on the flash drive:

rsync: rename "/mnt/usbdrive/sigcaps/.193702.bmp.054L9Z" -> "193702.bmp": No space left on device (28)
rsync: rename "/mnt/usbdrive/sigcaps/.193704.bmp.Bhe66U" -> "193704.bmp": No space left on device (28)
rsync: rename "/mnt/usbdrive/sigcaps/.193705.bmp.kFbOdQ" -> "193705.bmp": No space left on device (28)
rsync: rename "/mnt/usbdrive/sigcaps/.193706.bmp.OxtdXV" -> "193706.bmp": No space left on device (28)
rsync: rename "/mnt/usbdrive/sigcaps/.193707.bmp.2YxCd2" -> "193707.bmp": No space left on device (28)

For this example, there were actually 58,653 bmp files in the /keypos/sigcaps directory. I researched on the web and found nothing about a 32k file limit. Any ideas or suggestions will be greatly appreciated.

User avatar
TrevorH
Forum Moderator
Posts: 25808
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: rsync file limit

Post by TrevorH » 2019/03/06 22:18:44

You really really need to get off CentOS 5. It's been out of support for more than 2 years and there have been numerous high severity security vulnerabilities in the kernel (and other things) in the last 2 years that will never be fixed.

What filesystem is on the device that you are writing to? What is the output from df -i when it reports the problem?

But mainly, get off CentOS 5 NOW.
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

JimL
Posts: 2
Joined: 2019/03/06 19:05:42

Re: rsync file limit

Post by JimL » 2019/03/07 07:00:00

[Note that this is my first time posting on this forum and I saw no way to set the font to insure the columnar data was presented properly. Setting to monospace didn't help.]

I agree that all of the 87 customers running CentOS 5.X or even older versions should upgrade, but it's not my call. I wish it were. To upgrade would require many to probably also upgrade their hardware and definitely to upgrade the D3 Database Management system they use. This would require thousands of dollars, which many if not all aren't willing to spend. The general consensus is if it's working, don't mess with it.

Not all of our customers need the signature capture file backup feature. Regardless, the devices (flash drives) in question are typically off-the-shelf which are formatted for FAT32. Note this result from fdisk:

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 6383 7640064 c W95 FAT32 (LBA)

The results of the df -i command you asked about, after the errors started appearing is:

[root@DBMS-COL root]# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda2 5244736 283323 4961413 6% /
/dev/sda1 128520 53 128467 1% /boot
tmpfs 218723 1 218722 1% /dev/shm
/dev/sdb1 0 0 0 - /mnt/usbdrive

I left out all shared folder listings. They all showed 0 for Inodes, IUsed, and IFree also.

df -h showed the following for the mounted flash drive:

Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sdb1 7.3G 4.1G 3.3G 56% /mnt/usbdrive

User avatar
TrevorH
Forum Moderator
Posts: 25808
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: rsync file limit

Post by TrevorH » 2019/03/07 08:08:49

I suspect that the problem is your filesystem on the usb stick. I did some searching and tried to find out what the maximum number of directory entries per directory on FAT filesystems was but got too many conflicting answers.

Your problem with 87 customers on CntOS 5 is not going to go away unless you do something about it. It's dead. It's unmaintained. Would they still stay on Windows XP? And it's getting more and more out of date every day and that will only get worse. Those thousands of dollars you're talking about will pale into insignificance if they get hacked because of that - just ask Equifax et al how well running unmaintained systems went for them!
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

Post Reply