search for: filetree

Hi! I am running rsync 2.6.4 (on Debian sarge) and I am experiencing a strange behaviour. I am trying to create an identical filetree on the same filesystems with the single files being hardlinks to the source like this: rsync -vaH --progress --delete --stats --numeric-ids -x --link-dest=/path/to/filetree/ /path/to/filetree/ /path/to/current/ /path/to is one filesystem. This creates hardlinks for the files in /path/to/filetree/...

This really bogs down the system for several minutes each run, using 100% cpu and 50% of ram (this system has 3 gigs of memory!). What am I doing wrong here? file { "/etc/asterisk": links => "ignore", recurse => "true", replace => "false", source =>

I'm new but am already starting to accumulate utility functions for the fairly specialized kinds of data files with which I work. I'd like to keep those functions in a single folder, or filetree rooted at a specific folder under my $HOME (I'm running linux), for ease of * source()-ing * git commit to bitbucket * scp to clusters I'm wondering, 1 is there a canonical location for personal functions, notably on linuxen? 2 how can one make that location most easily available? or...

...age so I don''t forget. I should have it done this weekend. Dan Foster, Graham wrote: > I want to create a long UNC based path.. Server and top level will exist, > but subdirectories won''t (FileUtils.mkdir_p fails with a unc). I''d like to > remove a none empty filetree from a UNC (FileUtils.rm fails with a unc). I''d > like to recursively copy a filetree to a destination (FileUtils.cp_r fails > with a UNC) > > All work with mapped drive letters... So I need to create / re-use a drive > mapping and then iterate through my 1.7Tb of data. &gt...

...uot;) ... but this might be a very very rare case we will disable compression for this single file. 2) Rsync will need a new option for decompressing and stating the .rsc file tree. (single file, recursive) We should also offer options for validating .rsc files and converting a tree to a .rsc filetree. I am sending some compressor patches. I am very new to the rsync source, so here a list of what i did: options.c - added -X and -Z options (-Z is passed thru a server wenn using user@host.foo:/directory) flist.c: extension ".rsc" is added to every file/directory (in -Z mode) rsync...

...quot;share" (or as described in the documenation, from the "module"). In bound data is not filtered by the exclude directive - in fact, the exclude directive is completely ignored. To do in-bound exclude filtering for a share, you must either restrict access to the parts of the filetree using filesystem permissions and the uid and gid directives, or put your exclude clause(s) in your client-side rsync command. I've seen lots of folks complaining about "no syntax documentation for the exclude directive", which is actually inaccurate. The exclude syntax is indeed...

...r1 ??? ??? [-r--r--r--] text.txt ??? [drwxr-xr-x] target ??? [drwxr-xr-x] dir1 ??? [-rw-r--r--] text.txt But after "rsync --perms -r -v dir1 target" i've got an error message again: mkstemp "../target/dir1/.text.txt.AP4sMs" failed: Permission denied And the filetree: . ??? [dr-xr-xr-x] dir1 ??? ??? [-r--r--r--] text.txt ??? [drwxr-xr-x] target ??? [dr-xr-xr-x] dir1 <-- correct ??? [-rw-r--r--] text.txt <-- wrong Ok. So my final question is: Is it even possible what i want to do with rsync? The real situation is seriously far more comp...

...with another --link-dest issue: I am using dirvish (www.dirvish.org) to create daily backup on disk images. dirvish is using rsync with --link-dest pointing to the last good image. This creates images with hardlinks to unmodified files. So far so good. Now I want to create a "current" filetree with hardlinks pointing to the last image. rsync -vaH --delete --stats --numeric-ids -x --link-dest=/path/to/lastimg /path/to/lastimg /path/to/current This works except when an existing file has been modified and is now "new" (and not the n'th hardlink) in the image. This file is co...

Hello list, I have troubles with the daily backup of a modest filesystem which tends to take more that 10 hours. I have ext4 all over the place on ~200 servers and never ran into such a problem. The filesystem capacity is 300 GB (19,6M inodes) with 196 GB (9,3M inodes) used. It's mounted 'defaults,noatime'. It sits on a hardware RAID array thru plain LVM slices. The RAID array is

.../vgem_basic: Load and unload the module first lib/kmod: Fix error reporting for kmod load/unload lib: Disable MI_STORE_DATA_IMM for gen3 (i915g and i915gm) lib: Avoid actually throttling from igt_require_gem() igt/pm_rpm: Use libc 'ftw' rather than opencoding our own filetree walk igt/gem_userptr_blits: Errors from gup are permanent igt/gem_ringfill: Prime execbuf before measuring ring size igt/gem_exec_schedule: Do not overcommit batches to the ring igt/gem_exec_schedule: Exercise reordering with many priority levels igt/gem_exec_schedule:...