similar to: change of behaviour on rsync -R and top level symlinks?

For some reason, Rsync did not copy two specific file. Then I tried to specifically tell it to synchronize one of them and I get this result. *I* don't see any reason why to chose not to copy this file, but maybe on of you out there would see the obvious reason I am missing. dprweb> /usr/local/bin/rsync -vvv --stats -Pzrtpl --delete --password-file=/export/home/webuser/.appprod

Hello, We have a 3.0.21c samba server in a PDC role with ldap as the backend database, the server has been working without any problem for several weeks, but today it's started showing this log message: [2006/11/20 09:40:48, 0] tdb/tdbutil.c:tdb_log(772) tdb(/usr/local/etc2/samba_SACOU/private/secrets.tdb): tdb_lock failed on list 100 ltype=1 (Interrupted system call) [2006/11/20

Hi, We are testing the samba-3.0.23d in a samba server as role member in a domain with PDC (samba-3.0.20) and ldap as backend. The first tests don't left us join the machine in the domain, the following is showed: [root@machinetest bin]# ./net rpc testjoin -d 10 [2006/11/24 12:28:26, 5] lib/debug.c:debug_dump_status(391) INFO: Current debug levels: all: True/10 tdb: False/0

On Sat, Dec 19, 2015 at 1:53 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > These are supported on GK20A and GM107. > > Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> > --- > > Was a bit torn on where to place the enums... we're about to gut all > the xml definitions so this seemed appropriate for now. > > Tested on GK20A only. > >

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal

hello- i am using rsync via ssh to maintain a copy of a few directories on a remote server, and am getting an error when rsync tries to chmod a certain file following it's transfer. there are a couple of cases in which this occurring - below is one example. local machine is debian testing - rsync version 2.6.3 protocol version 28 remote machine is macos x 10.3.7 - rsync version 2.6.2

Brilliant, thanks very much!! Works fine. Dan On 6 Dec 2012, at 18:25, arun kirshna [via R] wrote: > Hi, > Your question is not very clear. I hope you are not looking for the subset option in summary(lm()). > If you want just the summary(), then use '&' or '|' > For e.g. > dat1<-read.table(text=" > opcorn Oilamt Batch Yield >

greetings. i have been three days now trying to add ext3 to an existing suse-7.3 machine. i am using suse's own 2.4.13 kernel source. here is what i have done: following install, i ran tune2fs -j /dev/hda2 (also hda3 and hda4). .journal files were created on each partition, apparently uneventfully. wishing to avoid ai irreversable situation, i initially edited /etc/fstab thusly:

Hi all. I'm sorry if this is a simple, obvious question, but I've looked around, and can not find an answer to this. What exactly are the false_alarms in the rsync summary? I am getting a number of false alarms in several of my rsync processes. Here's my output from one of my logfiles: total: matches=9724 tag_hits=741242 false_alarms=36 data=20850152 wrote 11731892 bytes read

Hi, I'm using rsnapshot 1.3.1 on a Synology Diskstation ds 107+. # uname -a Linux ds107 2.6.15 #832 Sat Mar 7 00:44:45 CST 2009 armv5tejl GNU/Linux rsnpahot uses rsync, on my box there is: # rsync --version rsync version 3.0.6 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit

I''ve seen this happen before, not sure why. I changed ''phy:'' to ''file:'' and it worked. I later rebooted and ''phy:'' worked again. So you might try ''file:'' rather than ''phy:''. -- Ray -----Original Message----- From: xen-users-bounces@lists.xensource.com

Hi, I just tried the 2.6.22-r1 candidate to test whether some bug I have hit in the past still exists. I did use 2.6.20.6 so far. So, I have cleanly rebooted to use the new kernel, after the machine came up I tried to mess with the bug, and had to reboot again to play with kernel commandline parameters. Unfortunately, on the next reboot fsck was schedules on my filesystem after 38 clean

Hello, I am having some trouble getting quota's to work. When I try to set the quota for a user, it does not show up when I run repquota. I am doing this on a Redhat (RHEL5) machine (I assume it is the same on Centos). I think I am missing a step, but this is what I am doing: (1) I add usrquota to the /etc/fstab file, then reboot LABEL=/home /home ext3 defaults,usrquota 1 2 (2) Verify

Hello, I have a perplexing problem. Im running Mandrake 10.0 and samba 3.0 setup as a domain controller. My client machines are XP Pro. I can join the domain and my "Homes" directory connects as it should. But that's all I can do. I have other shares that I can't access. For instance, I have a "downloads" share. Ive tried every conceivable setting but when I try

https://bugzilla.samba.org/show_bug.cgi?id=2781 Summary: rsync linked files not listed as uptodate Product: rsync Version: 2.6.5 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: idallen@idallen.ca

https://bugzilla.samba.org/show_bug.cgi?id=1582 Summary: rsync dry run cannot find missing folders, contradicts actual run. Product: rsync Version: 2.6.2 Platform: All OS/Version: IRIX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=7765 Summary: rsync error 23 without any real error Product: rsync Version: 3.0.7 Platform: PPC OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: nvbolhuis at aimvalley.nl

Help! I am running FC1, with a maxtor 160GB HD installed. Drive is only about a month old. I had just finished moving data from an older HD that was making some funny sounds and throwing some random errors. All was well. Last night we lost power for several hours and 1 machine's UPS/shutdown system didn't power down the workstation. The other 7 in our office did fine. The power

Hello, I had something interesting happen on a RH8 ext3 system I setup.I am at a loss to understand what happened. Info: This system has two IDE disks, partitioned identically, and the largest partition on each (/dev/hda3 and /dev/hdb3, 96GB each) was mirrored in a linux software RAID-1 configuration. It was running fine for many months. Then I updated the kernel and needed to reboot accordingly.

I must profane ignorance of complicated filesystem stuff, so feel free to call me out here. Booting a root ext3 drive produces the following message at boot: kinit: trying to mount /dev/root on /root with type ext2 EXT2-fs warning (device hda3): ext2_fill_super: warning: mounting ext3 filesystem as ext2 When remounted rw by init, everything looks fine: $ mount | grep hda3 /dev/hda3 on / type