similar to: 2.6.3: write error goes undetected

https://bugzilla.samba.org/show_bug.cgi?id=2116 Summary: rsync ignores write error Product: rsync Version: 2.6.3 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: jim@meyering.net QAContact:

I noticed that this topic appeared from time to time on the mailing list and that one patch exists (copy-devices.diff) from a previous thread which allowed rsync to operate with a source device file. The patch below, when combined with the 'copy-devices' patch, allows rsync to be operate between two device files. In our environment this is being used, along with LVM snapshots, to

Hi List, I had a need recently to efficiently synchronise between some large LUNs (boot drive disks) at two different datacentres. Solutions like drbd and $proprietary_array_vendors_software were overkill - we only needed (wanted!) to periodically synchronise these LUNs whenever major changes were generated on the source. On the other hand however, re-sending the entire disk contents each time

Hi, I have written a 'smallish' patch to implement the --inplace option as discussed on this mailing list at various points in the past. It makes a small modification to the sender algorithm so that it won't ask the receiver to relocate blocks from earlier in the file when running with the --inplace option. I would appreciate any testing and feedback people can provide! I

Since upgrading S4 DCs I am see the following message in log.samba - DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested: FFFFFFF8Unable to fetch value for secret BCKUPKEY_13bb48fc-0844-4736-9972-e26453333856, are we an undetected RODC? DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested:

On Mon, 19 Sep 2016 10:50:25 -0400 Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > On Mon, 2016-09-19 at 10:45 -0400, Adam Tauno Williams via samba > wrote: > > Since upgrading S4 DCs I am see the following message in log.samba - > > The message "Unable to fetch value for secret BCKUPKEY_13bb48fc-0844 > > -4736-9972-e26453333856, are we an

If it is that bug that you're referencing, besides obviously upgrading, you could try to patch it yourself. Whether or not you need to patch this, probably depends on whether or not your users are actually seeing issues. All that seems to happen is that it's entering a failure case when it hasn't actually failed. https://www.samba.org/samba/patches/ Cheers, Garming On 04/07/16

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: a5e1262c14c8b8b2e86d10d72c8edef705b390f5 Log message: 6346204 NFSv4 client suffers undetected write errors to full file system Files: update: usr/src/uts/common/fs/nfs/nfs4_vnops.c

dear smbfs maintainers! i sent this mail to you, since i got no answer from sending it to the "M:" entry of SMBFS. _______________ i had problems with setting permissions on a mounted smb file system. therefore i took a look at the smbfs code and a suspicious code part caught my eye. IMHO the patched line can't be correct, because comparing uids to gids doesn't make any sense.

I upgraded from 4.1.23 to 4.2.12 and am now getting (lots of) messages: Unable to fetch value for secret BCKUPKEY_, are we an undetected RODC? I found an almost identical message (titled: "Update samba4 from 4.1.17 to 4.2.1 failed") on the web from May 22, 2015 at: http://samba.2283325.n4.nabble.com/Update-samba4-from-4-1-17-to-4-2-1-failed-td4686215.html but saw no resolution other

Garming - thanks for your quick response. That link you gave me has Samba 3.x patches. I didn't notice any links to 4.x patches. Official Distro Releases are often behind the current stable release, generally. In fact, when I first installed Samba4 the Linux version was more recent than the Ubuntu version. This lag is probably due to abundance of caution and/or lack of manpower. I

Typically rsync exits and reports an error such as: rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: write failed on "/Volumes/Backup/big_file.dmg": No space left on device (28) rsync: connection unexpectedly closed (67174 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at /src/ rsync-3.0.5/io.c(600)

[resending, I made a typo in the list address] [ Please Cc: 624826-forwarded at bugs.debian.org on any replies ] Please see the bug report below. In short, when using --partial together with --update, an interrupted file will get the current timestamp, and hence when redoing the transfer the file is skipped due to --update. I've created a patch that sets the timestamp to 0 when a file

Hi list, I couldn't find anything related to this, on mailing lists or even bugzilla, so here it is. A problem with this combination exists in the new 2.6.3 where the bwlimit code got rewritten and is not present at <= 2.6.2. The problem is that on io.c:882 bwlimit_writemax is also used to control the bandwidth, but it is not initialized for the daemon mode. At options.c:772 you can see

Hiya, I can see it's a regular subject on this list. I, like others wanted to use rsync to synchronise two block devices (as it happens one lvm volume and one nbd device served by qemu-img on a remote host from a qcow2 disk image so that I can keep the old versions) As I couldn't find any report of it being done successfully, I'm just sharing my findings as it might benefit others.

If I scp from/to a server that has a banner using scp -q, it still shows the banner. If I ssh -q to the same server, the banner is skipped. scp -o "LogLevel quiet" does the trick, but is excessively cumbersome. - Morty

Dear List, the attached patch makes rsync of local folders almost as fast as cp. when rsync client and server has detected that they are working in local_server mode, they use local_socket, a unix domain socket pair, to pass the file descriptors of the synced files. the server uses the file descriptor it receives from the client to fast copy from src to dst file. on completion of every file fast

Thanks. I am still not sure whether option "with-acl-support" has been compiled in the smbd. The following is the output: Build environment: Built by: root@hxwu-dt-tt Built on: Tue Dec 23 15:00:40 CST 2003 Built using: gcc Build host: SunOS hxwu-dt-tt 5.9 Generic_112233-08 sun4u sparc SUNW,Sun-Blade-100 SRCDIR: /space/hxwu/swinstall/samba-3.0.1/source

Hi, I am trying to compile R as a shared library (need to run RMAGEML, which depends on SJava) on 64bit SUSE Linux 9.1 . I am using the source code for R 2.0.1 (Nov 15 04) > ./configure R_PAPERSIZE=LETTER R_BROWSER=/opt/kde3/share/applications/kde/konqbrowser.desktop --enable-R-shlib results in several errors (selected errors below), and make check also yields errors (at bottom) The errors

Has anyone successfully gotten the VFS modules to work under AIX 5.3 and Samba 3.0.x ? I have no problem compiling Samba 3.0.x and having it working; but when I set up a VFS module the following occurs: 1. In the log file I see: [2005/11/09 15:45:02, 0] lib/fault.c:fault_report(36) =============================================================== [2005/11/09 15:45:02, 0]