LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
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

Reply
 
Search this Thread
Old 01-12-2010, 12:02 PM   #1
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,547

Rep: Reputation: 37
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!
 
Old 01-12-2010, 12:08 PM   #2
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
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.
 
Old 01-12-2010, 12:11 PM   #3
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,547

Original Poster
Rep: Reputation: 37
I thought I needed to use the -a since I'm archiving to an external drive?
 
Old 01-12-2010, 12:14 PM   #4
uncle-c
Member
 
Registered: Oct 2006
Location: The Ether
Distribution: Fedora 14, Ubuntu , Slax 5.1.8, OpenSolaris, Centos 4.8
Posts: 296

Rep: Reputation: 30
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 12:15 PM.
 
Old 01-12-2010, 12:21 PM   #5
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,547

Original Poster
Rep: Reputation: 37
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?
 
Old 01-12-2010, 12:53 PM   #6
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Quote:
Originally Posted by rjo98 View Post
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?
 
Old 01-13-2010, 09:51 AM   #7
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,547

Original Poster
Rep: Reputation: 37
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?
 
Old 01-13-2010, 11:06 AM   #8
mostlyharmless
Senior Member
 
Registered: Jan 2008
Distribution: Slackware 14.1 (multilib) with kernel 3.15.5
Posts: 1,549
Blog Entries: 12

Rep: Reputation: 177Reputation: 177
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 11:07 AM. Reason: added info
 
Old 01-14-2010, 08:14 AM   #9
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,547

Original Poster
Rep: Reputation: 37
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?
 
Old 01-14-2010, 04:05 PM   #10
mostlyharmless
Senior Member
 
Registered: Jan 2008
Distribution: Slackware 14.1 (multilib) with kernel 3.15.5
Posts: 1,549
Blog Entries: 12

Rep: Reputation: 177Reputation: 177
I suppose you could have problems with permissions, but I haven't really had any. You could always chown/chgrp the files as needed.
 
Old 01-14-2010, 04:37 PM   #11
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,547

Original Poster
Rep: Reputation: 37
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?
 
Old 01-14-2010, 04:41 PM   #12
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,547

Original Poster
Rep: Reputation: 37
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.
 
Old 01-28-2010, 02:41 PM   #13
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,547

Original Poster
Rep: Reputation: 37
removing the -a got rid of it, closing thread.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't rsync to USB drive MooseMagnet Linux - Newbie 12 08-11-2008 07:03 PM
Rsync errors to USB drive jstars Linux - Server 8 12-23-2006 11:35 PM
rsync usb drive win95 fat32 PDock Linux - Software 1 06-12-2006 05:24 AM
rsync fails with USB hard drive Mad Scientist Linux - Software 3 03-27-2006 12:02 PM
How to Stop rsync From Doing chown? edwin11 Linux - Software 2 02-07-2006 06:00 AM


All times are GMT -5. The time now is 08:56 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration