Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
but didn't give that third line that it did earlier. does that mean its actually running this time since it didn't give that 3rd line?
sorry ignore my post regarding adding write permissions.
the cron is running, but part of it is failing.
the directory stuff/music cannot be opened and so the deletion is failing.
it cant be opened because of a permissions error i suspect
all it has is d then a bunch of dashes, which would explain that error
is there a way i can just have it ignore that error until i can figure out if I can just delete that directory since nobody can do anything with it?
you have to add some permissions before you can delete that directory....or you can just ignore it...send errors to /dev/null
my guess is that someone zeroed the permissions for a reason.
there are some rsync flags which can ignore this directory anyway.
looks like there is an ignore errors option in rsync i could use. but the rsync did eventually die with that third line of the error i posted earlier: rsync error: some files could not be transferred (code 23) at main.c(620)
Should i just have it rsync with the ignore errors?
Verify the entire drive? does that "skipping file deletion" error mean it won't delete ANY files or just one file in particular since the message only appeared once.
I was able to cp a file buried within my stuff folder to the root of the stuffbackup folder.
Verify the entire drive? does that "skipping file deletion" error mean it won't delete ANY files or just one file in particular since the message only appeared once.
AFAIK 1 file
However, can' you verify if the changes are made or not?
Not sure I understand what you asked, but if i did, I did a du -ch | grep total on both stuff and stuffbackup, there is a considerable difference between the two.
I gave it a shot with those 2 switches, but it didn't give me any other good info other than what was already noted earlier.
IO error encountered - skipping file deletion
rsync error: some files could not be transferred (code 23) at main.c(620)
How do i know what kind of IO error is found. it looks like its skipping deleting all files it should delete because of this. Without the --delete working I'm going to run out of space on my destination drive sorta soon.
just to try it I ran the rsync statement manually and got the following
opendir(stuff/music): Permission denied
IO error encountered - skipping file deletion
rsync error: some files could not be transferred (code 23) at main.c(620)
Maybe something got jacked up with permissions and that's the problem?
OK, problem solved kinda. It at least did the deletes on my second hard drive. What I ended up doing was chmod 700 on stuff/music so the user who had the crontab with my rsync would have permission. After I did that, i reran the rsync with -n -v and it was actually telling me it would delete stuff. so i removed the -n -v and what do you know, it did the deletes, but then gave the following messages still. At least I was able to free up the space on my secondary drive now, but why would I still be getting these messages?
opendir(stuff/music): Permission denied
delete_one: rmdir stuff/oldpics: Permission denied
rsync error: some files could not be transferred (code 23) at main.c(620)
OK, problem solved kinda. It at least did the deletes on my second hard drive. What I ended up doing was chmod 700 on stuff/music so the user who had the crontab with my rsync would have permission. After I did that, i reran the rsync with -n -v and it was actually telling me it would delete stuff. so i removed the -n -v and what do you know, it did the deletes, but then gave the following messages still. At least I was able to free up the space on my secondary drive now, but why would I still be getting these messages?
opendir(stuff/music): Permission denied
delete_one: rmdir stuff/oldpics: Permission denied
rsync error: some files could not be transferred (code 23) at main.c(620)
the problem is really in the messages itself. just read them then check perms/user on those folders
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.