LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-10-2011, 10:30 AM   #31
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Original Poster
Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546

Quote:
So I conclude its a problem or a bug with rsync...
When the source path contains spaces then enclose the entire source path in quotation marks. For the destination be sure the path ends with a slash.
 
Old 10-10-2011, 03:08 PM   #32
lpallard
Senior Member
 
Registered: Nov 2008
Posts: 1,016

Rep: Reputation: Disabled
I just tried a bit more to understand whats going on, and I must admit I am not sure...

The backup that is failing is due to the destination drive getting filled up. I am performing several other backups with the same strategy, both in my server and in my other machines. All are now working fine thanks to your help here!

Using a backup that is wiorking perfectly:

Source: /mnt/media-storage
Destination: /mnt/backup-media-storage

The source (/mnt/media-storage) contains *thousands* of files and folders with spaces in their file names. Most of these files are from both Mac & Windowz users. No nomenclature and naming standards whatsoever. The backup proceeds and finish without problems. du -hs and df -H are both reporting the source and destination are exactly same size.

Now to the backup that is eluding me:

Source: /mnt/mass-storage
Destination: /mnt/backup-mass-storage

The source is (according to du -hs) around 100GB. The source contains also thousands of files and folders, most of them coming from windows machines, they have spaces, underscores, dots (.) and other characters in their file names. There is no mount points, links or other black magic that would make a folder size increase when copied. Just a plain file tree.

This backup is running as we speak. tail -f on the rsnapshot log does not report anything strange. The destination drive (250GB) is almost full (81% full = 203GB) and keep increasing... Absurd.

For some obscure reasons, rsync freaks with my files & folders that are in the source (/mnt/mass-storage) and goes wild.

cp -r successfully copied the content of the source to another locations without problems. Result was exacly same size, as I would expect from rsync.

Quote:
When the source path contains spaces then enclose the entire source path in quotation marks. For the destination be sure the path ends with a slash.
The source path has no spaces. Like I said, I cant guarantee every files & folders in my computers do not have spaces in their filenames, and it would be ridiculous to do so. The destination has a trailing slash as you can see in my conf file below:

Code:
# Mass storage (temp drive) backup rsnapshot config file
config_version	1.2
snapshot_root	/mnt/backup-mass-storage
no_create_root	1
cmd_cp		/bin/cp
cmd_rm		/bin/rm
cmd_rsync	/usr/bin/rsync
cmd_logger	/usr/bin/logger
cmd_ssh		/usr/bin/ssh
rsync_short_args	-aH
link_dest	1
retain		monthly	1
verbose		2
loglevel	4
logfile		/var/log/rsnapshot-backup-mass-storage
lockfile	/var/run/rsnapshot-backup-mass-storage.pid

backup		/mnt/mass-storage/	localhost/
 
Old 10-10-2011, 03:24 PM   #33
lpallard
Senior Member
 
Registered: Nov 2008
Posts: 1,016

Rep: Reputation: Disabled
I *think* I know what happens...

The source contains several old torrent files I started several years ago, but never finished and I un-officially abandoned them. So this is what Ive seen with a specific file. There are many hundreds similar files...

Source:

Filesize as reported by Thunar: 675MB
Filesize as reported by du -hs: 404MB

Destination:

Filesize as reported by Thunar: 675MB
Filesize as reported by du -hs: 675MB

I think the problem is that I ve based my operations on df -H which reported a total of 100GB while this value must have been a similar report as du -hs did on the source file...

I suspect (I am 99% sure) that the problem is NOT rsync (I have been blaming it all along, sorry old friend) but rtorrent or the filesystem. As far as I know, when you download a file with torrents, it allocate the space of the file on the drive, but until the download is complete, only portions of the file are really there.

Anybody could confirm or clarify me on the torrent rsync relationship?
 
  


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
Properly removing SATA hard drives(hot-swap) galapogos Linux - Hardware 3 08-26-2009 02:40 AM
Does IDE/SATA/SCSI drives support hot-swapping ? exceed1 Linux - Hardware 10 10-19-2008 09:33 PM
Hot-swappable SATA Drives in RAID 5 on Linux? Synesthesia Linux - Hardware 11 01-06-2006 06:14 PM
hot swap for adding random hard drives? PATA, SATA, SCSI? Oo.et.oO Linux - General 1 11-05-2005 10:38 AM
Hot swapping? gauge73 Linux - Hardware 3 08-10-2005 12:52 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:00 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration