Comments on: Data Synchronization/Backup Headaching http://motespace.com/blog/2005/09/24/data-synchronizationbackup-woes/ Disclaimer: The following web space does not contain my own opinions, merely linguistic representations thereof. Sun, 13 Mar 2011 07:12:38 +0000 hourly 1 https://wordpress.org/?v=4.6.1 By: mote http://motespace.com/blog/2005/09/24/data-synchronizationbackup-woes/comment-page-1/#comment-1282 Wed, 19 Apr 2006 16:57:57 +0000 http://fairuz.isi.edu/blog/index.php/archives/2005/09/24/data-synchronizationbackup-woes/#comment-1282 Thanks, Alex! This is great! A quick check shows that mounting as uid=username also gets rid of those warning messages when you copy/move files in the shell from linux filesystems to fat.
-Nick

]]> By: Alex Tomlins http://motespace.com/blog/2005/09/24/data-synchronizationbackup-woes/comment-page-1/#comment-1279 Wed, 19 Apr 2006 15:33:53 +0000 http://fairuz.isi.edu/blog/index.php/archives/2005/09/24/data-synchronizationbackup-woes/#comment-1279 I was having this problem just now, and I found this solution to it:

http://lists.samba.org/archive/rsync/2005-October/013710.html

Basically: Linux won’t let you set an arbitrary mtime on a file that you don’t own (even if you have write permission to it). On a vfat filesystem everything is owned by the same user (usually root). The solution for me was to mount the filesystem with the uid my user using the uid=username option in /etc/fstab.

It’s now working well without complaining.

Hope that helps,
Alex

]]>