[SOLVED] Still having rsync errors to external drive
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi jlinkels. I know the df -h shows it, because that was how i saw how much free space was on it to report in my first post.
I dont know if this has any barring, but it seems like the rsync starts to work fine, but the longer it runs, the more those errors pop up, then it happens so much i cant even tell what's going on because it scrolls so fast.
I really don't understand why it would say no space where there is hundreds of GB's available, and the other message I forgot to check to see if that directory actually existed before i left today.
I had it as fat32 because I need to transfer it between linux mac and pc's without having to worry about permissions. Do you think ntfs would be better to handle all those files and transfer between all those os's.
Could it be a "number of directory entries" issue? I notice that your failing mkdir appears to be based on a persons name. I believe max number of directory entries under fat32 is 65535, but as long-filename support can result in a single file/subdir taking up several entries, it can be much smaller than that.
If this is the case then perhaps splitting your batches further might work around this. Reports suggest anywhere in the region of 10-20K entries could be enough to trigger this issue.
it could be. i went with fat32 so i could transfer it between XP, Mac OSX, and Linux. how can i tell how many directories there currently are on the entire drive? I know some of the jpg's have long file names.