Linux - Newbie This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
01-12-2010, 01:02 PM
|
#1
|
Senior Member
Registered: Jun 2009
Posts: 1,795
Rep:
|
rsync chown errors to fat32 usb drive
I'm trying to back up a directory to a fat32 usb external hard drive. My rsync keeps throwing errors that it can't do a chown on any of the files on the fat32 usb drive. I just want it to copy the files, no permissions since fat32 doesn't allow for permissions. What rsync switches should I use? I'm using r a v now. Thanks!
|
|
|
01-12-2010, 01:08 PM
|
#2
|
LQ Guru
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594
|
At a glance, I'd suggest removing the -a argument. That's what's probably causing the errors. As you noted, FAT doesn't allow for permissions such as ownership etc.., so you need to copy the stuff while IGNORING the permissions.
See the rsync man page for more details.
|
|
|
01-12-2010, 01:11 PM
|
#3
|
Senior Member
Registered: Jun 2009
Posts: 1,795
Original Poster
Rep:
|
I thought I needed to use the -a since I'm archiving to an external drive?
|
|
|
01-12-2010, 01:14 PM
|
#4
|
Member
Registered: Oct 2006
Location: The Ether
Distribution: Ubuntu 16.04.7 LTS, Kali, MX Linux with i3WM
Posts: 299
Rep:
|
You can still use the "r" ( recursive) or "t" ( maintain the files last modified time) option. Definitely do not use the "a" option (keep group & user ownership) as Ggirl rightly said.
Last edited by uncle-c; 01-12-2010 at 01:15 PM.
|
|
|
01-12-2010, 01:21 PM
|
#5
|
Senior Member
Registered: Jun 2009
Posts: 1,795
Original Poster
Rep:
|
Ok I'm trying it now with -r. Never used -t before. If I don't use -t will it change the modified time to right now, then make subsequent rsyncs take longer because it thinks they're different files?
|
|
|
01-12-2010, 01:53 PM
|
#6
|
LQ Guru
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594
|
Quote:
Originally Posted by rjo98
If I don't use -t will it change the modified time to right now, then make subsequent rsyncs take longer because it thinks they're different files?
|
Sounds reasonable, but I personally am not certain HOW rsync determines whether a file is the same or not. mtime seems a good candidate though.
Something you might consider for all this, especially for in the event that you wish to RESTORE any of this backup at some time to its original location and state more easily, would be to reformat your FAT drive to something more befitting the sort of backup that you are sending to it.
Is there anything preventing you from reformatting the backup drive to an Ext* filesystem, or some filesystem that supports the permissions required?
|
|
|
01-13-2010, 10:51 AM
|
#7
|
Senior Member
Registered: Jun 2009
Posts: 1,795
Original Poster
Rep:
|
The permissions are of no importance to me. The files are only on this Linux server because it was the only one that had enough space to copy them all to originally.
I need to be able to move the drive possibly back and forth between Windows, Mac, and Linux machines, and I think only FAT32 will go between them all without issue?
Does anyone else know for sure if I should or shouldn't use the -t to make future rsync's go quicker?
|
|
|
01-13-2010, 12:06 PM
|
#8
|
Senior Member
Registered: Jan 2008
Distribution: Arch/Manjaro, might try Slackware again
Posts: 1,859
|
Quote:
I think only FAT32 will go between them all without issue?
|
I'm pretty sure Macs can read NTFS, as can linux. Ext3 can be read with ext2ifs, a utility for windows; there's probably a utility for the Mac too.
Edit: yep, just checked google, ext2ifs anf ntfs-3g run on Macs too.
Last edited by mostlyharmless; 01-13-2010 at 12:07 PM.
Reason: added info
|
|
|
01-14-2010, 09:14 AM
|
#9
|
Senior Member
Registered: Jun 2009
Posts: 1,795
Original Poster
Rep:
|
Thanks. wouldn't using ntfs preserve some set of permissions, which could cause problems as i move the external drive back and forth between computers on different workgroups and domains?
|
|
|
01-14-2010, 05:05 PM
|
#10
|
Senior Member
Registered: Jan 2008
Distribution: Arch/Manjaro, might try Slackware again
Posts: 1,859
|
I suppose you could have problems with permissions, but I haven't really had any. You could always chown/chgrp the files as needed.
|
|
|
01-14-2010, 05:37 PM
|
#11
|
Senior Member
Registered: Jun 2009
Posts: 1,795
Original Poster
Rep:
|
Well I have it running now in verbose mode, and it keeps throwing a bunch of mkstemp failed no such file or directory (2) and mkdir failed no space left on drive (28).
I know before I started the rsync there was a hundreds of GBs of space on the external drive, and my data set i'm trying to copy is around 200GB, so there's plenty of room. Any idea what these errors are about? Or should I maybe open a new post with a new subject?
|
|
|
01-14-2010, 05:41 PM
|
#12
|
Senior Member
Registered: Jun 2009
Posts: 1,795
Original Poster
Rep:
|
Actually for the mkstemp errors, its showing the real filenames with a . then random letters after it, assuming rsync writes a temp file with the extra stuff at the end, then removed the extra stuff after it writes successfully.
|
|
|
01-28-2010, 03:41 PM
|
#13
|
Senior Member
Registered: Jun 2009
Posts: 1,795
Original Poster
Rep:
|
removing the -a got rid of it, closing thread.
|
|
|
All times are GMT -5. The time now is 05:44 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|