https://bugzilla.samba.org/show_bug.cgi?id=8308
Wayne Davison changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #8 from Wayne Davison
https://bugzilla.samba.org/show_bug.cgi?id=8308
--- Comment #7 from Wayne Davison 2014-04-20 21:10:54 UTC ---
Created attachment 9862
--> https://bugzilla.samba.org/attachment.cgi?id=9862
Don't pass an inactive dir to change_local_filter_dir()
See if this patch fixes the issue you're seeing.
https://bugzilla.samba.org/show_bug.cgi?id=10555
Wayne Davison changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from Wayne Davison
https://bugzilla.samba.org/show_bug.cgi?id=10552
Wayne Davison changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10372
Wayne Davison changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=9103
--- Comment #3 from Wayne Davison 2014-04-19 17:22:46 UTC ---
If someone would like to research how code checks a crtime, coming up with a
patch that changes the existing crtime.diff patch would be appreciated (or even
just reporting the result of t
https://bugzilla.samba.org/show_bug.cgi?id=10552
Wayne Davison changed:
What|Removed |Added
Status|NEW |ASSIGNED
Severity|normal
https://bugzilla.samba.org/show_bug.cgi?id=10557
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10557
--- Comment #3 from Kevin Korb 2014-04-17 19:37:06 UTC
---
OK, I was speaking from a Linux perspective. I have no idea what OSX uses as
root's home dir. Simply put, under sudo you are running as root and root has a
different home dir therefore a
https://bugzilla.samba.org/show_bug.cgi?id=10557
--- Comment #2 from kesten 2014-04-17 18:44:27 UTC
---
Thanks for the faster-than-light response.
I mounted the samba file server to my mac as recommended in
https://discussions.apple.com/message/25112468#25112468
I then symlink and chown to kbr
https://bugzilla.samba.org/show_bug.cgi?id=10557
--- Comment #1 from Kevin Korb 2014-04-17 18:35:45 UTC
---
The key here is the sudo. ssh will always look to ~/.ssh/config but once you
sudo your ~ is /root instead of /Users/kbroughton. Duplicate your
~/.ssh/config in ~root/.ssh/config and it s
https://bugzilla.samba.org/show_bug.cgi?id=10557
Summary: .ssh/config settings are incompletely applied with -e
or --rsh
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: no
https://bugzilla.samba.org/show_bug.cgi?id=10552
--- Comment #2 from dougmi...@cox.net 2014-04-17 15:26:35 UTC ---
Just adding that when using fast storage such as an SSD and/or a slow processor
like in some NAS boxes, the gap can widen quite a lot. Here are my times on my
2.6GHz Core i7 Ivy Brid
https://bugzilla.samba.org/show_bug.cgi?id=10552
--- Comment #1 from John Pierman 2014-04-17 12:34:03 UTC ---
Confirmed:
Without -z avg over 3 runs (real0m5.998s)
With -z avg over 3 runs (real0m8.490s)
On Mon, Apr 14, 2014 at 4:10 PM, wrote:
> https://bugzilla.samba.org/show_bug.cgi?
https://bugzilla.samba.org/show_bug.cgi?id=9103
--- Comment #2 from jaba 2014-04-17 01:18:50 UTC ---
Hi Wayne, I'd like to thank you for picking this up. What's the current
status? I would also love to see Samba preserving NTFS file creation
timestamps – many people have gathered files over the
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #25 from roland 2014-04-16 20:56:50 UTC ---
so, if kernel update fixed it we should consider this as being resolved
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because:
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #24 from Colin Rice 2014-04-16 20:31:10 UTC ---
Originally it was hanging even without the i, but since then I've wiped the
backup drive completely, and upgraded my kernel from 3.13.6 to 3.14 and it is
no longer hanging without the
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #23 from Colin Rice 2014-04-16 19:24:39 UTC ---
Created attachment 9854
--> https://bugzilla.samba.org/attachment.cgi?id=9854
sysrq blocked tasks
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You a
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #22 from Colin Rice 2014-04-16 19:19:09 UTC ---
I removed the verbosity and it stopped hanging. If I drop back down to -i
again, it does hang.
I still use dm-crypt for the partition.
--
Configure bugmail: https://bugzilla.samba.o
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #21 from roland 2014-04-16 18:54:51 UTC ---
> You should press alt-sysrq-w when the deadlock happen to see if there are
> any processes deadlocked in the kernel. If yes, send me the stacktrace of
> those processes.
>
> If there are n
https://bugzilla.samba.org/show_bug.cgi?id=10555
Summary: checksum-reading.diff causes rsync to segfault with
large amount of files
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
S
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #20 from roland 2014-04-15 21:37:37 UTC ---
what do you mean with "no longer hanging"? you mean you do not use dm-crypt for
the target partition anymore and so the problem is solved for you?
it would be interesting to find out why the
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #13 from mlus...@redhat.com 2014-04-15 15:11:51 UTC ---
I can confirm that this issue is caused by compiling rsync with system provided
zlib in F20. Archlinux package doesn't contain zlib in dependencies,and
therefore I suppose the packa
https://bugzilla.samba.org/show_bug.cgi?id=10552
Summary: Sender checksum calculation significantly slower with
compression enabled
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
S
https://bugzilla.samba.org/show_bug.cgi?id=10551
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #19 from Colin Rice 2014-04-13 20:13:55 UTC ---
The extra verbosity was added as an attempt to debug the deadlocks. However as
it is not longer hanging without the extra verbosity, it works for me.
--
Configure bugmail: https://bugzil
https://bugzilla.samba.org/show_bug.cgi?id=10522
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10527
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10551
Summary: Daemon infinite loop when no matched user in secrets
Product: rsync
Version: 3.1.1
Platform: x64
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #17 from roland 2014-04-13 09:24:09 UTC ---
apparently, there seems to exist a deadlock patch for dmcrypt for about 5
months, but it seems it did not enter mainline kernel yet, so probably your
distro is also missing it:
https://github
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #16 from Colin Rice 2014-04-13 09:02:32 UTC ---
Hmm, I'm pretty sure the problem appeared sometime in 3.13 since before then
rsync was working fine. I'll contact the dm-crypt people and ask for help.
--
Configure bugmail: https://bugz
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #15 from roland 2014-04-13 09:01:04 UTC ---
i have no idea on how to proceed further.
if you use an older distro, try reproducing that on a recent one, with recent
kernel version.
maybe the dm-crypt people have an idea what to do to f
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #14 from Colin Rice 2014-04-13 08:43:26 UTC ---
If I use an ordinary cp -rx everything seems to work.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You ar
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #13 from roland 2014-04-13 08:20:50 UTC ---
can you reproduce the hang without using rsync, e.g. by doing an ordinary cp ?
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail be
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #12 from Colin Rice 2014-04-13 08:07:19 UTC ---
My apologies, I wrote to the wrong mount. btrfs on a raw partition works fine.
So it appears the problem is related to dm-crypt.
--
Configure bugmail: https://bugzilla.samba.org/userpref
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #11 from Colin Rice 2014-04-13 05:47:05 UTC ---
I tried with btrfs on top of a raw partition as the destination and it
deadlocked.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #10 from Colin Rice 2014-04-13 01:59:27 UTC ---
It appears that the problem is writing to a partition mounted on top of
dm-crypt. I tried btrfs and ext4 on top of dm-crypt and they both deadlocked.
Ext4 on top of a raw partition was fi
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #9 from roland 2014-04-12 21:26:37 UTC ---
>Like try and backup a portion of the file system?
no, retry with one of the filesystems being standard ext3/4 to see if source or
target fs is the culprit.
btrfs is still considered experime
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #8 from Colin Rice 2014-04-12 16:51:44 UTC ---
(In reply to comment #7)
> can you tell if there is some special type of mount involved?
It is copying from an ecrypted partition mounted with dm-crypt to another
encrypted partition mounte
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #7 from roland 2014-04-12 10:28:30 UTC ---
can you tell if there is some special type of mount involved?
what type of filesystem on src / destination ?
large files ?
for how long did you wait for finish ? (
https://bugzilla.samba.org
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #6 from Colin Rice 2014-04-10 23:48:08 UTC ---
(In reply to comment #5)
> lsof | grep rsync is showing no open files
I was running lsof as a local user not root.
lsof | grep rsync is showing it stuck on the same file after repeated run
https://bugzilla.samba.org/show_bug.cgi?id=10545
--- Comment #2 from Erik 2014-04-10 15:08:31 UTC ---
Thanx for your respons.
I dont understand your remark at dont rsync -c. I think i'm doing the
following:
What i do with this command is:
su - rsync -c "/usr/bin/rsync -avh --delete --progre
https://bugzilla.samba.org/show_bug.cgi?id=10522
--- Comment #3 from J.R. 2014-04-10 02:50:13 UTC ---
Created attachment 9840
--> https://bugzilla.samba.org/attachment.cgi?id=9840
revised patch detect-renamed.diff
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
-
https://bugzilla.samba.org/show_bug.cgi?id=10522
--- Comment #2 from J.R. 2014-04-10 02:49:02 UTC ---
I can confirm this problem.
I suggest increasing the Severity of this bug to "Critical" because it causes
data to be lost without the user requesting this.
The problem is that a small section o
https://bugzilla.samba.org/show_bug.cgi?id=10545
--- Comment #1 from Kevin Korb 2014-04-09 20:11:58 UTC
---
I am really not sure I understand what you are describing here so I will give
general backup with rsync advice...
1. Don't rsync -c unless you really really have to. It is horribly
inef
https://bugzilla.samba.org/show_bug.cgi?id=10545
Summary: Rsync first time deletes files, second time it
synchronates files with same name
Product: rsync
Version: 3.0.9
Platform: x64
OS/Version: Linux
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=8308
--- Comment #6 from John 2014-04-09 04:38:00 UTC ---
Oh god this is awful. But it is making more sense now - these macros are
supposed to be accessing various members internal to the file_struct structure.
This is hideous though. I cannot believe w
https://bugzilla.samba.org/show_bug.cgi?id=8308
--- Comment #5 from John 2014-04-09 04:03:11 UTC ---
woops, it's not just a 64bit pointer being treated as 32.
When you run macro F_DEPTH(file) you're actually subtracting the size of a
32bit integer, ie 4 bytes, but file is a pointer to structure
https://bugzilla.samba.org/show_bug.cgi?id=8308
--- Comment #4 from John 2014-04-09 03:05:08 UTC ---
from rsync.h:
union file_extras {
int32 num;
uint32 unum;
};
#define REQ_EXTRA(f,ndx) ((union file_extras*)(f) - (ndx))
#define F_DEPTH(f) REQ_EXTRA(f, 1)->num
f
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #5 from Colin Rice 2014-04-09 02:53:35 UTC ---
lsof | grep rsync is showing no open files
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA con
https://bugzilla.samba.org/show_bug.cgi?id=8308
--- Comment #3 from John 2014-04-09 02:04:50 UTC ---
Some slightly better info from gdb, caught program with bad value of dir_depth,
before crash. There is no way this dir suddenly out of the blue has a depth of
1622.
Looks like i need to recompile
https://bugzilla.samba.org/show_bug.cgi?id=8308
--- Comment #2 from John 2014-04-09 01:38:35 UTC ---
Should've actually added a comment on this bit:
http://sourceforge.net/p/luckybackup/discussion/873564/thread/864b0b61/
"Indeed, rsync seems to bring this error up when specific filter rules
(in
https://bugzilla.samba.org/show_bug.cgi?id=8308
--- Comment #1 from j...@mensa.org.au 2014-04-09 01:31:48 UTC ---
I also see this bug with the latest sources for: 3.1.1pre1 and i have a
directory tree i can reproduce this bug with easily, on a local machine. No
remote transfer required.
It is rel
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #3 from roland 2014-04-08 21:34:43 UTC ---
does it always deadlock at the same file/position ?
please check with losf |grep rsync, to see at which file rsync got stuck...
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #4 from roland 2014-04-08 21:42:19 UTC ---
pardon, typo - it should read lsof|grep rsync
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA co
https://bugzilla.samba.org/show_bug.cgi?id=10518
--- Comment #8 from Eric Chaput 2014-04-06 13:47:15 UTC ---
I struggled with the same problem trying to rsync a particular large VM file.
Even though your random data trick didn't help it got me thinking about the
issue and I thought couldn't we j
https://bugzilla.samba.org/show_bug.cgi?id=10540
Summary: --max-transfer and --create-freespace options for
working with limited space
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: All
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #2 from Colin Rice 2014-04-03 03:40:24 UTC ---
Also happens with rsync 3.1.1pre1
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for
https://bugzilla.samba.org/show_bug.cgi?id=10532
Summary: Rsync fails with older version.
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: cor
https://bugzilla.samba.org/show_bug.cgi?id=10527
--- Comment #1 from Colin Rice 2014-03-30 09:48:36 UTC ---
Created attachment 9820
--> https://bugzilla.samba.org/attachment.cgi?id=9820
rsync strace output
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You ar
https://bugzilla.samba.org/show_bug.cgi?id=10527
Summary: Rsync Deadlock when copying files
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component:
https://bugzilla.samba.org/show_bug.cgi?id=10518
--- Comment #7 from Bram Matthys 2014-03-29 20:10:00 UTC
---
Ok that random data trick didn't help, or not enough. I'll be using the -W
option for now then, to workaround the problem.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cg
https://bugzilla.samba.org/show_bug.cgi?id=10522
--- Comment #1 from John Pierman 2014-03-28 19:10:39 UTC ---
I'm sorry typo'd the rsync command, left out the --detect-renamed flag.
Should be
rsync -rvzhtSin --detect-renamed /tmp/test1/ /tmp/test2/
(In reply to comment #0)
> Scenario:
>
> File
https://bugzilla.samba.org/show_bug.cgi?id=10522
Summary: --detect-renamed patch is causing deletions as if a
'delete flag' was supplied, when none have been
Product: rsync
Version: 3.1.1
Platform: x86
OS/Version: All
https://bugzilla.samba.org/show_bug.cgi?id=10518
Wayne Davison changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #5 from Wayne Davison
https://bugzilla.samba.org/show_bug.cgi?id=10518
--- Comment #6 from Bram Matthys 2014-03-28 17:25:22 UTC
---
Thanks for your explanation.
The file in question is an image file (ext4) used by a VM. Since the file is
fresh and not all is in use, it is likely that this file still contains a few
t
https://bugzilla.samba.org/show_bug.cgi?id=10518
--- Comment #4 from Bram Matthys 2014-03-28 12:18:55 UTC
---
Thanks for the suggestion. That post says the patch was added in rsync in
August 2013, so that should be included in the 3.1.1pre1 of end of January.
Looking through the git changelog s
https://bugzilla.samba.org/show_bug.cgi?id=10518
--- Comment #3 from roland 2014-03-27 22:29:42 UTC ---
large file involved?
have a look at this:
http://www.anchor.com.au/blog/2013/08/out-tridging-tridge/
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are
https://bugzilla.samba.org/show_bug.cgi?id=10518
--- Comment #2 from Bram Matthys 2014-03-26 20:24:14 UTC
---
And obviously I meant I'm using 3.1.1pre1, not beta1...
Anyway, if you need the (gzip'ed) core file, just let me know. I don't want to
attach it here due to it likely containing sensiti
https://bugzilla.samba.org/show_bug.cgi?id=10518
--- Comment #1 from Bram Matthys 2014-03-26 20:18:05 UTC
---
Just realized I ls'd the wrong file. Not that it matters much, so just FYI:
# ls -al /data/vm/green/data-ll.img
-rw-r--r-- 1 libvirt-qemu libvirt-qemu 214748364800 Mar 26 21:18
/data/vm/
https://bugzilla.samba.org/show_bug.cgi?id=10518
Summary: rsync hangs (100% cpu)
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P5
Component: core
https://bugzilla.samba.org/show_bug.cgi?id=10495
Wayne Davison changed:
What|Removed |Added
QAContact|rsync...@samba.org |
--
Configure bugmail: https://bugzilla.s
https://bugzilla.samba.org/show_bug.cgi?id=10495
Wayne Davison changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10495
Filipus Klutiero changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
https://bugzilla.samba.org/show_bug.cgi?id=10495
Wayne Davison changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10495
--- Comment #13 from Filipus Klutiero 2014-03-22 05:18:35
UTC ---
That's not what I meant. Here is what this example will do on a simple
directory having 2 files matching *.c:
$ ls -lR
.:
total 4
drwxr-xr-x 2 test test 4096 mar 22 01:04 bar.c
-rw
https://bugzilla.samba.org/show_bug.cgi?id=10507
Summary: Structured Output (for Simpler Parsing)
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Compon
https://bugzilla.samba.org/show_bug.cgi?id=10495
--- Comment #12 from Paul Slootman 2014-03-19 06:57:03 UTC ---
(In reply to comment #11)
> No, [it] would transfer *some* files matching the pattern *.c from the current
> directory to the directory src on the machine foo.
>
> At least directories
https://bugzilla.samba.org/show_bug.cgi?id=10332
--- Comment #3 from Orion Poplawski 2014-03-18 16:18:28
UTC ---
I'm guessing a dupe of bug 10372?
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contac
https://bugzilla.samba.org/show_bug.cgi?id=10372
Orion Poplawski changed:
What|Removed |Added
CC||mlus...@redhat.com
--- Comment #12 from
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #11 from Orion Poplawski 2014-03-18 15:51:41
UTC ---
I take that back, this is caused by using the system zlib in Fedora 20. Still
poking around.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You a
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #10 from Orion Poplawski 2014-03-18 15:01:33
UTC ---
I get the same failure using the provided zlib in 3.1.1pre1.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: -
https://bugzilla.samba.org/show_bug.cgi?id=10495
Filipus Klutiero changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #9 from Harvey 2014-03-15 12:05:23 UTC ---
Additional comment: Archlinux uses zlib 1.2.8
https://www.archlinux.org/packages/core/x86_64/zlib/
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are rec
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #8 from Harvey 2014-03-15 12:03:16 UTC ---
I don't know how to test that either. I am on archlinux, the PKGBUILD is here:
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/rsync
The configure statement
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #7 from rudy.metz...@xs4all.nl 2014-03-15 08:22:31 UTC ---
(In reply to comment #5)
> Please check if the version you're testing links against zlib or includes the
> zlib that ships with rsync. I'd imagine that it is trying to use the s
https://bugzilla.samba.org/show_bug.cgi?id=10372
Wayne Davison changed:
What|Removed |Added
CC||or...@cora.nwra.com
--- Comment #6 from Wa
https://bugzilla.samba.org/show_bug.cgi?id=10497
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #5 from Wayne Davison 2014-03-14 23:25:27 UTC ---
Please check if the version you're testing links against zlib or includes the
zlib that ships with rsync. I'd imagine that it is trying to use the system's
zlib, and the code that tries
https://bugzilla.samba.org/show_bug.cgi?id=10495
Wayne Davison changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10496
--- Comment #3 from Kevin Korb 2014-03-14 21:54:00 UTC
---
That makes sense. I was testing on Gentoo without any SELinux.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because:
https://bugzilla.samba.org/show_bug.cgi?id=10496
--- Comment #2 from Benjamin Gilbert 2014-03-14
21:51:17 UTC ---
Yes, it is:
$ getfattr -d -m - b/1
# file: b/1
security.selinux="unconfined_u:object_r:user_home_t:s0"
user.rsync.%stat="100664 0,0 0:0"
user.rsync.security.selinux="unconfined_u:ob
https://bugzilla.samba.org/show_bug.cgi?id=10497
Summary: rsync fails to sync certain sparse file combinations
with compression
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Sever
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #4 from Harvey 2014-03-14 17:33:15 UTC ---
I can confirm that the error only raises if compression is invoked. Doing the
same file transfer without -z in the commandline runs without errors.
--
Configure bugmail: https://bugzilla.samb
https://bugzilla.samba.org/show_bug.cgi?id=10495
Filipus Klutiero changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #3 from rudy.metz...@xs4all.nl 2014-03-14 12:58:28 UTC ---
I can confirm this bug. I am using
rsync -rltDvz --stats -e ssh "$BACULA_LOCAL/" "$RSYNCTO:$BACULA_REMOTE" \
1>>$LOGFILE 2>>$ERRFILE
which results in this error
rsync: [
https://bugzilla.samba.org/show_bug.cgi?id=10496
--- Comment #1 from Kevin Korb 2014-03-14 07:33:09 UTC
---
It works for me.
Can you verify if it is actually setting the extended attributes with getfattr?
If not then you probably need the user_xattr mount option.
--
Configure bugmail: https:
https://bugzilla.samba.org/show_bug.cgi?id=10495
Wayne Davison changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10495
--- Comment #7 from Filipus Klutiero 2014-03-14 04:39:59
UTC ---
Sorry if I was unclear, but I didn't mean to say that rsync's behavior should
be changed. I do believe that users would expect rsync to transfer directories
by default, but this does
https://bugzilla.samba.org/show_bug.cgi?id=10495
--- Comment #6 from Kevin Korb 2014-03-14 03:41:18 UTC
---
Because the user probably doesn't want *.c to match files and directories. If
they want *.c recursively they probably need the include/exclude example that
is listed elsewhere. This is e
601 - 700 of 4233 matches
Mail list logo
