[EMAIL PROTECTED] wrote:
> And we're talking about multiple servers in multiple locations talking
> to multiple hosts of different brands and hardware chipsets. It's not
> related to a *specific* *anything* hardware-wise on *either* end. The
> *only* thing in common is RHEL4!
Do they traverse a common switch to reach your backup server?
> This is not related to other hosts on the network. For my testing, I
> was testing with *2* computers on an isolated switch. It's not
> external-network related. Something to do with the network code of
> RHEL4? Sure. But not something to do with a bad external anything:
> there aren't any to be bad.
I thought you said you booted knoppix and had the same result.
> I've done my first tests in this regard. Still fails on stock CentOS
> 4.1. Moving to 4.2 next. I'm not at the location where my test lab is,
> so it will have to wait until tonight.
Are you doing updates before testing? I don't have a non-updated
machine to compare but I see nothing like this and I have a lot of
Centos boxes.
> It's not perfectly on-topic, but I would think that it is very relevant
> to anyone who wants to use rsync with RHEL4!
Do the RHEL4's have current updates?
> Mine too. I've researched and found that each system involved seems to
> be running the stock RHEL4 kernel:
>
> # uname -a
> Linux amherst-smb 2.6.9-5.EL #1 Wed Jan 5 19:22:18 EST 2005 i686 i686
> i386 GNU/Linux
> #
>
> I find it hard to believe that I haven't updated a *single* RHEL
> system's running kernel. I *know* I've done updates on several of
> these. Either the kernel did not need to be updated when I did the
> updates, or I did not apply it. That is likely: I'm not a big fan of
> upgrading systems that work.
I disagree. The people who go to the effort of creating the update
packages know more about the system in question than I do, and they
thought it was worth the trouble. This is particularly true of
'enterprise' systems where the updates are generally hand-picked bug
fixes backported to the version levels of the distribution packages so
you don't have surprising behavior changes. I've forgotten how up2date
works though - the kernel might be excluded unless you explicitly select
it, or it may install but not change your grub config to become the default.
> It is **VERY** easy to reproduce this problem. For *anyone*. Download
> CentOS 3.8 CD1 and do a minimal load on a PIII computer. Download
> CentOS 4.0 (or 4.1) CD1 and do a minimal load on a PIII computer. Do an
> rsync using the command line I've supplied. It's very likely that it
> will fail first time. Create a couple of gig worth of data (a minimal
> install is only 500MB) and I *guarantee* you will fail: I've never had
> anything P4 1.6GHz or slower finish more than 1GB of data...
Does it have to be a combination of 3.x <-> 4.x or do the other
permutations do the same for you? I have both but across a router from
each other. But I really don't expect to see any problem with any
combination here - my main backuppc box runs centos4 and backs up both
centos3 and 4 targets.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
