Displaying 20 results from an estimated 2000 matches similar to: "about rsyncing of block devices"
2009 Oct 15
1
PATCH: --write-devices to allow synchronising to a block device
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
2004 Sep 02
1
--partiall-dir not behaving like it ought too
Hi,
I have awaited the new release inorder to use the -"-partial-dir" option.
But after testing it seems that it does not behave like it says on the tin.
It will correctly move and rename the interrupted file to the declared
directory, but it will not
attempt to use it when the client attempts to rsync the file again.
I have a Solaris 8 box running as a server (Matthew), and another
2002 Aug 05
5
[patch] read-devices
Greetings,
I'd like to propose a new option to rsync, which causes it to read
device files as if they were regular files. This includes pipes,
character devices and block devices (I'm not sure about sockets). The
main motivation is cases where you need to synchronize a large amount of
data that is not available as regular files, as in the following scenarios:
* Keep a copy of a block
2008 Sep 09
3
directories not correctly recognized rsync-3.0.4
Hi,
I'm running rsync-3.0.4 on my UNIX system. I've just updated from rsync-2.6.9.
I'm facing a general problem with the execution of files during a transfer process.
The situation: 2 Directories (dir1 and dir2) on one machine with a some files in dir1 which shall be translated to dir2.
rsync does not correctly recognize dir1 and dir2 as directories. It tries to transfer dir1 as a
2002 Jun 21
1
small security-related rsync extension
Included below is a shar archive containing two patches that together:
1) make backup files get their setuid and setgid bits stripped by
default
2) add a "-s" option that allows backup files to continue to have
these privileges
This means that if you update a collection of binaries with rsync, and
one or more of them has a local-root security problem, the backup
file(s) created when
2008 Dec 05
0
rsync patch to allow content from one device file to be synced to another device file
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
2005 Jan 05
1
rsync filename heuristics
On 5 Jan 2005, Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Tue, 2005-01-04 at 18:24 +0100, Robert Lemmen wrote:
> > hi rusty,
> >
> > i read on some webpage about rsync and debian that you wrote a patch to
> > rsync that let's it uses heuristics when deciding which local file to
> > use. could you tell me whether this is planned to be included in
2016 Jul 25
2
[Bug 12036] New: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior
https://bugzilla.samba.org/show_bug.cgi?id=12036
Bug ID: 12036
Summary: Multiple --link-dest, --copy-dest, or --compare-dest
flags produce incorrect behavior
Product: rsync
Version: 3.1.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component:
2012 Feb 18
4
FADV_DONTNEED support
While going through an old todo list I found that these patches had fallen by
the way-side. About a year ago I initiated a discussion[1] with the Linux
kernel folks regarding the lack of any useable fadvise support on the kernel
side. As a result, I was observing extremely poor performance on my server
after backup as executable pages were being swapped out in favor of data
waiting to be flushed
2004 Jan 24
2
[PATCH] --links-depth for rsync
Hello,
about a year ago I ran into situation where there's a "metadirectory"
containing directories and symlinks to files. There was a need to mirror
the contents of files and directories gathered via symlinks to this
metadirectory, regular mirroring of the tree wouldn't do any good.
The attached patch gives the user ability to define how many symbolic
links rsync should follow
2001 Nov 13
2
direct write patch
I have attached a patch that supports a new "--direct-write" option.
The result of using this option is to write directly to the destination
files, instead of a temporary file first.
The reason this patch is needed is for rsyncing to a device where the
device is full or nearly full.
Say that I am writing to a device that has 1 Meg free, and a 2 meg file
on that device is out of date.
2011 Feb 05
2
rsync not reporting diskfull error
I am involved with the development of lbackup. This message to the rsync mailing list is related to the following thread on the lbackup-disccussion mailing list : http://tinyurl.com/lbackup-discussion-diskfull
Essentially, I am curious to if any one using rsync 3.0.7 on Mac OS (10.6) Server has experienced an out of disk space error and not had a message similar to the following reported :
>
2023 May 17
1
[PATCH] Add --omit-{device,special}-times options
Similar to --omit-{dir,link}-times:
--omit-device-times omit device files from --times
--omit-special-times omit sockets and fifos from --times
Also, fix corner case that allows --omit-dir-times to be ignored. See
unchanged_attrs() and recv_generator()'s call to try_dests_non().
Marc.
diff -aNpRruz -X /etc/diff.excludes rsync-3.2.7/generator.c devel-3.2.7/generator.c
---
2004 May 10
2
read error produces null-byte-filled destination file
I've run into a bug in the IO handling when reading a file. Suppose I
have a file that lives on an NFS filesystem. That filesystem is NOT
being exported with auth=0 permissions. So, if I try to access a file
as root, it successfully opens the file, but subsequent reads fail with
EACCES. This produces a destination file full of null bytes. I
noticed this with 2.5.7, but checked 2.6.2 as
2008 Mar 02
3
congrats!
Thanks Wayne and everybody,
This is a huge boost to have a modern rsync for OSX. We're all
grateful. Rob D
PS I did notice that we lost the bsd flags test in 3.0. It was ok in
pre10.... thanks again
bbouncer
Verifying: basic-permissions ... ok
Verifying: timestamps ...
Sub-test: modification time ... ok
ok
Verifying: symlinks ... ok
Verifying:
2002 May 04
1
A simpler move-files patch
In an effort to get my long-desired move-files functionality into rsync,
I have created a version of my patch that runs as an extra pass at the
end of the processing. This results in a simpler set of changes to
rsync.
I still think it would be nice to have incremental deletions during
large transfers (as my first patch provides), but acceptance of this
patch would relegate such quibbling to a
2008 Feb 15
4
Revised flags patch
Hi,
first of all, sorry for taking so long. Unfortunately, some other tasks
kept coming up. Anyway, attached is the version of the flags patch, that
is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9
release.
I've included the option name change from the repository, so the
option is now called --fileflags. Improved from the previously
distributed version is the
2012 Jun 09
2
[patch] NFSv4/ZFS ACLs
This is a PoC patch for NFSv4/ZFS ACLs.
The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs
without requiring a new command line option
NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is
present a separate POSIX draft ACL will not be present and there are new
APIs
to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and
POSIX
ACLs in
2002 Apr 03
3
metadata in dryrun mode
As I reported a while back rsync doesn't handle metadata (permissions and
ownership) in dryrun mode.
I offered to make a patch and that offer still stands. I didn't have the
time for it until now and want to pick it up again. I had some ugly hack
back then but I want to redo it in a clean way.
I would like some input on my thoughts.
IMHO, it would be ideally if the check for dry_run
2005 May 31
0
[Bug 2758] New: "File exists" error using options -b and --backup-dir with device files.
https://bugzilla.samba.org/show_bug.cgi?id=2758
Summary: "File exists" error using options -b and --backup-dir
with device files.
Product: rsync
Version: 2.6.4
Platform: All
OS/Version: AIX
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: