Question about rsyncing to a slightly different folder structure on target
Hi all, Ok, if this isn't possible with some kind of wildcard, I can adjust the target manually, but if I can just modify the command to allow for the different folder structure on the target, I'd rather do that. I'm incrementally rsync'ing my mailstore from the old server to the new server, doing testing along the way. The command I'm currently using is: rsync -rltgovDHP --delete --delete-excluded --exclude-from '/path/to/excludes.txt' /mnt/oldvmail/example.com/ /var/vmail/example.com/ On the old server, dovecot is configured to just use .../example.com/user for the maildirs. On the target server, I want to change this to .../example.com/user/Maildir Is there a way to modify the above command, so that rsync automatically syncs what is currently in .../example.com/user to .../example.com/user/Maildir using wildcards or something? Thanks -- Best regards, */Charles/* -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 10290] Regression since 3.0.9: send_xattr_request: Assertion `f_out = 0' failed
https://bugzilla.samba.org/show_bug.cgi?id=10290 --- Comment #5 from Moritz Bunkus mor...@bunkus.org 2013-12-31 12:26:56 UTC --- Unfortunately I haven't been able to narrow down the test case. I've spent the last couple of days trying to make it as small as possible. The bug occurs when I rsync a whole dirvish host directory (beneath the host directory there is one directory per day when a backup was run, and beneath those is a tree of the whole backed up file system from that day hard-linked to the previous day's backup). It also happens for the same file each and every time (I've run »rsync -vvhaxHAX --delete src/ dest/« and the last file name output before that assertion has been the same each and every time). Apart from the files having a moderate hard link count (~ 28) I cannot find anything special about it. As a matter of fact it happens with a file from Dropbox' cache directory (~/Dropbox/.dropbox.cache/…). As soon as I try to narrow down the test case the bug disappears. What I've tried is to move all the .dropbox.cache directories out from their huge dirvish structure into a new directory structure that was laid out the same as the dirvish structure. For example, orignal file structure: /backup/dirvish/hostname/root/20131226/tree/home/mosu/Dropbox/.dropbox.cache, similar names for other days; temporary structure: /temp/backup/dirvish/hostname/root/20131226/tree/home/mosu/Dropbox/.dropbox.cache. I've only moved each and every .dropbox.cache directory there was in the original structure to its place in the temporary structure; no other directories were populated in the temp structure. I reasoned that those Dropbox cache files should only have hard links to files in the other Dropbox cache directories but not to any normal file outside of those directories. Unfortunately as soon as I rsync'ed that temporary structure the assertion wasn't triggered. Now I'm out of ideas of how to narrow it down. If you have any please let me know and I'll give them a try. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html