I pulled the latest version down from the CVS tree and noticed that the
patch is already incorporated.
Compiled on HP-UX 11i, it works great!
Thanks for all your help,
Don
From: "Steve Bonds" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: HP-UX 11i and largefiles on
On Mon, 2 Aug 2004, Wayne Davison wayned-at-samba.org |Rsync List| wrote:
> Would anyone who is seeing this problem please try out the patch that is
> attached to this bugzilla bug:
>
> https://bugzilla.samba.org/show_bug.cgi?id=1536
I gave it a test and it seems to work fine on HPUX 11.0. I
Would anyone who is seeing this problem please try out the patch that is
attached to this bugzilla bug:
https://bugzilla.samba.org/show_bug.cgi?id=1536
You'll need to re-run configure and re-build before re-testing. (I
appended this patch to the bugzilla bug back on the 30th, but the
bugzill
On Tue, 27 Jul 2004, Wayne Davison wayned-at-samba.org |Rsync List| wrote:
> This would seem to indicate that the mkstemp() call is not compatible
> with large file systems, probably because it is not calling the right
> open() call in the library (on systems where large- file support
> redefines
On Thu, 29 Jul 2004, Chris Shoemaker c.shoemaker-at-cox.net |Rsync List| wrote:
> On Wed, Jul 28, 2004 at 10:57:58AM -0700, Steve Bonds wrote:
> > The mkstemp man page suggests using tmpfile() instead, which
> > generally means that HP won't fix any problems.
> >
> > - mktemp(3C)
> > Rema
On Wed, Jul 28, 2004 at 10:57:58AM -0700, Steve Bonds wrote:
> > HP-UX?
>
> Alas, no. The mkstemp man page suggests using tmpfile() instead, which
> generally means that HP won't fix any problems.
>
> - mktemp(3C)
> Remarks:
> These functions are provided solely for backward compat
On Tue, 27 Jul 2004, Wayne Davison wayned-at-samba.org |Rsync List| wrote:
> This sparked a memory, and back in 2002 someone reported a similar
> problem for AIX. They worked around it by undefining the
> HAVE_SECURE_MKSTEMP define in config.h and rebuilding rsync. This would
> seem to indicate
Attached is some public domain source code that tests mkstemp() to see if
it functions properly by creating a 2GB sparse file in /tmp, first via the
normal open()/lseek()/write() pathway, then using
mkstemp()/lseek()/write().
Perhaps this could be migrated into an rsync test case? My only concern
On Wed, Jul 28, 2004 at 02:06:45AM -0500, John Van Essen wrote:
> Wayne - why is the "write failed" message not being displayed?
A local-to-local transfer treats the sending side as the client, so
that's the only side that lets output messages. My guess is that the
error message from the receiver
On Tue, 27 Jul 2004, Steve Bonds <[EMAIL PROTECTED]> wrote:
>
> bigfile
> rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown":
> Broken pipe (32)
> rsync error: error in rsync protocol data stream (code 12) at io.c(902)
> The receiver backtrace is:
>
> -
> (gdb) bt
> #0
On Tue, Jul 27, 2004 at 03:23:44PM -0700, Steve Bonds wrote:
> I've been able to duplicate this problem using the CVS version of rsync
> that was current as of about 2000 UTC today (July 27 2004)
That's some good detective work, Steve!
-chris
>
--
To unsubscribe or change options: http://lists.
On Tue, Jul 27, 2004 at 03:23:44PM -0700, Steve Bonds wrote:
> write(4, 0x400a0b37, 1) . ERR#27 EFBIG
Very nice -- that's what we need to know. This sparked a memory, and
back in 2002 someone reported a similar problem for AIX. They worked
around it by undefining the HAVE_SECURE_MKSTEMP
"Steve Bonds" writes:
> This is what I would expect to see if the VXFS filesystem was not created
> with the "largefiles" option-- but it was. (And I double-checked.) Other
> utilities (e.g. "dd") can create large files just fine.
>
> I haven't seen anything obviously wrong with write_file or
>
I've been able to duplicate this problem using the CVS version of rsync
that was current as of about 2000 UTC today (July 27 2004)
This was on an HPUX 11.0 system, not 11i.
When running:
./rsync --archive -v --progress /home/sbonds/bigfile
/home/sbonds/dest_dir/.
I get:
-
bigfile
rsync: wr
From: "Don Malloy" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: HP-UX 11i and largefiles on rsync 2.6.2
Date: Fri, 23 Jul 2004 12:16:02 -0400
It still shows as bad breakpoint..
server2 # ./gdb /archive1/rsync 6835
HP gdb 2.1
AIL PROTECTED]>
To: Don Malloy <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: HP-UX 11i and largefiles on rsync 2.6.2
Date: Thu, 22 Jul 2004 16:29:23 -0700
On Thu, Jul 22, 2004 at 04:27:57PM -0400, Don Malloy wrote:
> server2 # ./rsync -a --progress --stats file1.db /var/op
On Thu, Jul 22, 2004 at 04:27:57PM -0400, Don Malloy wrote:
> server2 # ./rsync -a --progress --stats file1.db /var/opt/ignite
What I want is the backtrace when the rsync that is failing dies so we
can (hopefully) figure out why it is dying. In the above command the
client should be the sender,
#12 0x11b7c in do_cmd (cmd=0x0, machine=0x0, user=0x0, path=0x4000aed0
"/var/opt/ignite", f_in=0x7f7f0668,
f_out=0x7f7f066c) at main.c:319
#13 0x13664 in start_client (argc=1, argv=0x4000aa00) at main.c:911
#14 0x13c74 in main (argc=2, argv=0x4000aa00) at main.c:1110
Is that what you
On Wed, Jul 21, 2004 at 02:21:27PM -0400, Don Malloy wrote:
> Hopefully this is of more help to you.
Unfortunately I haven't been able to get rsync to fail in the update of
a large file, and the system call trace you provided didn't tell me
anything helpful in narrowing down what is going wrong.
Just trying a few more things, if you reduce the number of v's, it continues
to the same point in the file, but instead of going to sleep, it errors out.
Here's an output:
server2 # /tmp/rsync -avvv --progress --stats file1.db /var/opt/ignite
building file list ...
[sender] make_file(file1.db,*,
)
server2 # fsadm -F vxfs /var/opt/ignite
largefiles
From: Craig Barratt <[EMAIL PROTECTED]>
To: "Don Malloy" <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: HP-UX 11i and largefiles on rsync 2.6.2 Date: Tue, 20 Jul 2004
14:11:56 -0700
"Don Malloy" writes:
&
"Don Malloy" writes:
> I just tried the build from the nightly tar file:
> rsync-HEAD-20040720-1929GMT.tar.gz
>
> It failed at 2144075776 bytes each time I tried. I've attached the tail from
> the tusc again. Here it the output of the rsync:
I haven't been following this thread, so I might be
ut to call exit(12)
---
From: Wayne Davison <[EMAIL PROTECTED]>
To: Don Malloy <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: HP-UX 11i and largefiles on rsync 2.6.2
Date: Tue, 20 Jul 2004 12:30:27 -0700
On Mon, Jul 19, 2004 at 01:1
On Mon, Jul 19, 2004 at 01:13:55PM -0400, Don Malloy wrote:
> Interestingly enough, now it stops dead when it hits 2146631680 bytes
> transferred. [...] Any ideas?
I haven't been able to duplicate the problem you're seeing using the cvs
version of rsync. I'll try a patched 2.6.2 next. You may wi
to send it.
Command syntax at run time is:
server2 # /usr/local/bin/tusc -T "" -v -f /tmp/rsync -av file1.db
/var/opt/ignite > /tmp/tusc.out 2>&1
From: "Don Malloy" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: HP-UX 11i and largefiles on rsync 2.6.2
Dat
io.c, line=836): about to call exit(12)
----------------
HP-UX 11i and largefiles on rsync 2.6.2
Don Malloy nixuser23 at hotmail.com
Thu Jul 15 20:30:50 GMT 2004
Don Malloy <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: HP-UX 11i and largefiles on rsync 2.6.2
Date: Thu, 15 Jul 2004 09:28:10 -0700
On Wed, Jul 14, 2004 at 04:46:41PM -0400, Don Malloy wrote:
> The rsync transfers always fail at the 2GB mark.
There is a bug in the large-file supp
On Wed, Jul 14, 2004 at 04:46:41PM -0400, Don Malloy wrote:
> The rsync transfers always fail at the 2GB mark.
There is a bug in the large-file support of 2.6.2 that is fixed by the
attached patch. Either apply it using "patch" or manually edit the
size_t to OFF_T manually, recompile, and give th
blic Licence for details.
Is it supposed to show 32-bit system inums? Will this require a re-compile
and how do I force that parameter to 64-bit?
Thanks again,
Don
From: "Steve Bonds" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: HP-UX 11i and largefiles on rsync 2.6.2
Date:
On Wed, 14 Jul 2004, Don Malloy nixuser23-at-hotmail.com |Rsync List| wrote:
> The rsync output is as follows:
>
> server1 # /tmp/rsync --rsync-path=/tmp/rsync --stats file1.db
> server2:/archive1
> rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown":
> Broken pipe
**
Hello,
I'm running HP-UX 11i on an rp74xx. It's 64-bit.
C compiler is as follows:
B3901BA B.11.11.03 HP C/ANSI C Developer's Bundle for HP-UX 11.i (S800)
B3913DB C.03.30.02 HP aC++ Compiler (S800)
/usr/bin/cc:
LINT B.11.11.02 CXREF B.11.11.02
HP92453-01 B.11.11.02 HP C Compiler
31 matches
Mail list logo
