similar to: rsync-bugs and unclear semantics when copying multiple source-dirs to one target

I have found a nasty bug when a file, which is in some of many sources, shall be copied to a target. The linux-Version works well but rsync 2.5.{2|5|6} under solaris9 (gcc 2.95.3) and darwin (gcc 3.1) do not. The decision which file (out of which src) shall be copied depends on the number of src dirs given on the command line. This bug bytes us very hard, because we decided to rely on rsync

When I do rsync -av --backup --backup-dir=/dir1/dir2/Backup \ /dir1/dir2/dir3 machine:/dir1/dir2/dir3 I get /dir1/dir2/Backup/dir3/... /Backup/dir3/dir4/... i.e. the tree under 'dir3' (my source tree) gets created under .../Backup. This is fine. But when I do the same thing with a single file like rsync -av --backup --backup-dir=/dir1/dir2/Backup \ /dir1/dir2/file

Hi mabi, Some questions: -Did you by any chance change the cluster.quorum-type option from the default values? -Is filename.shareKey supposed to be any empty file? Looks like the file was fallocated with the keep-size option but never written to. (On the 2 data bricks, stat output shows Size =0, but non zero Blocks and yet a 'regular empty file'). -Do you have some sort of a

Hello All, I have an off topic question about rsync and was wondering if i can get some kind person help with it. I have two servers with each server have three same directories on them /dir1/ /dir2/ /dir3/ . How would i achieve this by using rsync? I have tried rsync -avrt --delete server_ip:/dir1/ /dir2/ /dir3/ /dir1/ /dir2/ /dir3/ this does not do anything except give errors. Someone on IRC

Thank you Ravi for your fast answer. As requested you will find below the "stat" and "getfattr" of one of the files and its parent directory from all three nodes of my cluster. NODE 1: File: ?/data/myvolume-private/brick/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/OC_DEFAULT_MODULE/filename.shareKey? Size: 0 Blocks: 38 IO Block: 131072 regular

Hello, I just wanted to ask if you had time to look into this bug I am encountering and if there is anything else I can do? For now in order to get rid of these 3 unsynched files shall I do the same method that was suggested to me in this thread? Thanks, Mabi ? ??????? Original Message ??????? On May 17, 2018 11:07 PM, mabi <mabi at protonmail.ch> wrote: > ?? > > Hi Ravi,

On 04/09/2018 05:40 PM, mabi wrote: > Again thanks that worked and I have now no more unsynched files. > > You mentioned that this bug has been fixed in 3.13, would it be possible to backport it to 3.12? I am asking because 3.13 is not a long-term release and as such I would not like to have to upgrade to 3.13. I don't think there will be another 3.12 release. Adding Karthik to see

On 05/23/2018 12:47 PM, mabi wrote: > Hello, > > I just wanted to ask if you had time to look into this bug I am encountering and if there is anything else I can do? > > For now in order to get rid of these 3 unsynched files shall I do the same method that was suggested to me in this thread? Sorry Mabi,? I haven't had a chance to dig deeper into this. The workaround of

Hello all; I'm attempting to migrate from an existing NT4 file server to a Debian GNU / Samba setup. I've performed this many times before with great success, however this particular case in proving to be something of a problem. On the test setup, all seems to be working fine apart from one particular application. The application in question reports only "Run-time error

Hi, we have a problem with permissions migrating from a custom 2.4 kernel Linux distro with Samba 2.2.5 to OpenSuSE 10.3 (with samba 3.0.26). We used to have directories like this (relative to the Samba share): /root/dir0/dir1/dir2/dir3/userdir1-1/userdir1-2 'root' and all it's parent directories have '0755' Linux permission. dir0-dir3 all have '0711' permissions

I''m running 2.6.6 on a red hat EL3 system. using the following command, rsync -rlptDvzL --stats --include=a/ --include=a/dir/ --include=a/dir/symlink/ --include=a/dir/symlink/dir2/ --include=a/dir/symlink/dir2/dir3/ --exclude=''**'' /export/stuff remote::stuff I expect the "symlink" (which is really a symbolic link to a directory) to be preserved on the

I want to send a subset of directories sepcified in "include" arguments to a client, but I am creating all the peer and parent directories as well, although they are empty - here is basically what I'm doing. assuming I have /staging/upgrade/dir1, /staging/upgrade/dir2 and /staging/upgrade/dir3 on the source tree. --include "*/" -include upgrade/dir1/** -include

I want to use --min-size to copy just large files (and their necessary parent directories), but everything I've tried copies *all* the source directories, and creates them empty on the destination even if they don't have any big files in them. I only want the minimal directory hierarchies that contain the big files. This doesn't work: $ rm -rf /tmp/foo $ rsync -ai --min-size

On 04/09/2018 05:09 PM, mabi wrote: > Thanks Ravi for your answer. > > Stupid question but how do I delete the trusted.afr xattrs on this brick? > > And when you say "this brick", do you mean the brick on the arbitrer node (node 3 in my case)? Sorry I should have been clearer. Yes the brick on the 3rd node. `setfattr -x trusted.afr.myvol-private-client-0

Hi Ravi, Please fine below the answers to your questions 1) I have never touched the cluster.quorum-type option. Currently it is set as following for this volume: Option Value ------ ----- cluster.quorum-type none 2) The .shareKey

Greetings, I have created several scripts which needs to be packaged. I have done my groundwork on rpmbuild Let us say I have 4 directories with scripts in them dir1, dir2, dir3 and dir4 I want to create different packages which will contain the compiled code (err.. shc) pack1: dir1,dir2 pack2: dir1,dir3 pack3: dir1,dir3 I want the resulting rpm packages will be residing elsewhere (perhaps

Again thanks that worked and I have now no more unsynched files. You mentioned that this bug has been fixed in 3.13, would it be possible to backport it to 3.12? I am asking because 3.13 is not a long-term release and as such I would not like to have to upgrade to 3.13. ??????? Original Message ??????? On April 9, 2018 1:46 PM, Ravishankar N <ravishankar at redhat.com> wrote: > ??

Good morning all, We are moving our web server from novell to unix (solaris) and will be using samba to allow users to edit web pages. Our samba instance authenticates using ADS and the users do not necessarily have accounts on the server itself. We are attempting to allow users to map a single samba share but only see the directories they have read access to (see configuration below). Any

Hi All, I am writing a backup program for my computer. brief outline is as follows. Running ubuntu 10.04 2 main partitions, / and /home, both ext3. 1 external usb hdd, ext3, mounted to /backups/main. once every couple of days, rsync backs up, using following command, everything worth backing up in / and /home partitions to a folder /backups/main/Full. command: "rsync -vrhRupElog

On 04/09/2018 04:36 PM, mabi wrote: > As I was suggested in the past by this mailing list a now ran a stat and getfattr on one of the problematic files on all nodes and at the end a stat on the fuse mount directly. The output is below: > > NODE1: > > STAT: > File: