Sent from my iPad
--
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
very nice and I expect it to save 10's of GB per archive going forward.
Kevin was right. --whole-file was the default when source and
destination are specified as local paths.
On 5/22/13, Allen Supynuk wrote:
> Kevin,
>
> I will try again over a remote connection to see i
ote:
> On Tue 21 May 2013, Allen Supynuk wrote:
>>
>> ## 1) Start with an empty filesystem
>>
>> $ df -h .
>
> Note that you need to be using "btrfs filesystem df ."
> for reliable numbers; the normal df does not take into account
> background cleanups
I have been doing some experiments with rsync on btrfs, a
copy-on-write file system that is approaching or having just achieved
production-ready status depending on your requirements.
For my purposes the reliability appears by almost all accounts to be
there, and the compression alone makes it ver
This looks like a shell issue to me.
Try
> rsync "root@192.168.101.53:/Volumes/WD-Daten/XserveMirror/Satz/Akzidenzen\
> 2012/" "/Volumes/PromiseRAID/Satz/Akzidenzen 2012" 2>&1
And
> rsync "root@192.168.101.53:'/Volumes/WD-Daten/XserveMirror/Satz/Akzidenzen
> 2012/'" "/Volumes/PromiseRAID/S
with a warning instead of stop
part way thru with an error. I realize that the current behavior is the correct
default.
-Allen
Sent from my iPad
On Feb 2, 2013, at 11:09, francis.montag...@inria.fr wrote:
>
> Hi.
>
> On Fri, 11 Jan 2013 03:08:13 +0100 Allen Supynuk wrote:
&
Will do.
On 1/11/13, Karl O. Pinc wrote:
> On 01/11/2013 09:08:52 AM, Allen Supynuk wrote:
>> > While you're at it, why not a more generic
>> > --ignore-errno foo
>> > where foo is (a defined subset of) the Posix error numbers
>> > listed in errno(3).
> While you're at it, why not a more generic
> --ignore-errno foo
> where foo is (a defined subset of) the Posix error numbers
> listed in errno(3). The names, alternately, could be
> used.
>
> So your application would use
>
> --ignore-errno EACCES
Karl,
I love this suggestion, and will do it t
> [..] Rsync does
> continue after it encounters a permission denied error. It just can't
> copy that particular file/directory but it will continue on through
> the tree.
I know it continues, but it gives a non-zero return code (23) that
indicates that errors occurred.
The error code indicates a
I work on software that archives gigabytes of files to multiple sites.
Occasionally one or two files have no read permissions:
% ls -l dir/foo
--w---+ 1 abcserve myusers 11222 Jan 10 03:14
The error message is:
rsync: send_files failed to open "/dir/foo" (in xxx): Permission denied (13)
rsy
10 matches
Mail list logo
