Value too large for defined data type
Jeff.Le...@adic.com
compile option to HAVE_OFFSET64_T resolved the problem.
Thanks,
Jeff
Message: 1
Date: Wed, 9 Oct 2002 16:19:00 -0700
From: jw schultz <j...@pegasys.ws>
To: rs...@lists.samba.org
Subject: Re: Value too large for defined data type
On Wed, Oct 09, 2002 at 07:26:44AM -0700, Jeff.Le...@adic.com wrote:
> Howdy,
>
> I am just starting to use rsync and now have an rsync
> server set up to back up our various machines. I recently
> started getting an error that is confusing and I can't
> find info documented on it. I searched the news group and
> found it mentioned but no solution yet.
>
> I get the error when sync'ing from a Solaris 8 machine to
> my Solaris 8 server.
>
> stat space/sunpci/drives/F.drive/docs/StorNext/LinuxPort/devfs.README.txt
:
> Value too large for defined data type
> stat space/sunpci/drives/F.drive/docs/StorNext/StorNextNotes.doc : Value
too
> large for defined data type
>
> I also see the same error going from our IRIX 6.5.15 machine, and the
error
> is seen on a directory
> vs a file:
> stat apps1/fsdev.cliff/jleuschner/phoenix/ver_2.1.0B57/phtm/ver : Value
too
> large for defined data type
> stat apps1/fsdev.cliff/jleuschner/phoenix/ver_2.1.0B57/phtm/ver/CVS :
Value
> too large for defined data type
More fields were enlarged in stat than just filesize. I'm
guessing but i'd say your rsync was built with
HAVE_OFFSET64_T undefined. As near as i can tell this
message appears to be comming from libc (i don't have an AIX
or Solaris machine to check). The enlarged field could be
one that rsync doesn't care about but you might want to
rebuild rsync making sure that HAVE_OFFSET64_T is defined so
that it uses stat64.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: j...@pegasys.ws
Remember Cernan and Schmitt
--__--__--
Message: 2
From: "Efficient solution" <Onlin...@effcientsolution.com>
To: rs...@samba.org
Subject: Web Hosting Solutions for businesses of all sizes $96.00/Year
Date: Thu, 10 Oct 2002 00:52:06
<html>
<head>
<title>Efficient Solution</title>
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">
</head>
<body bgcolor="#FFFFFF" text="132A63" leftmargin="0"
topmargin="0" marginwidth="0" marginheight="0">
<div align="center"><br>
<table width="100" border="0" cellspacing="0"
cellpadding="0" bgcolor="#FFFFFF" height="341">
<tr>
<td><a target="_blank"
href="http://www.efficientsolution.com"><img border="0"
target="_blank"
src="http://www.efficientsolution.com/mailout/head.gif"></a>
</td>
</tr>
<tr>
<td height="1"> </td>
</tr>
<tr>
<td> </td>
</tr>
<tr>
<td><center>
<font face="arial" size="5">Solutions for businesses of
all sizes</font>
</center>
<center><font face="arial" size="3" color=#B40403><b>
Secure - Reliable - Guaranteed Up
Time - Firewall Protection</b></font></center></td>
</tr>
<tr>
<td> </td>
</tr>
<tr>
<td height="161">
<table width="100%" border="0" cellspacing="0"
cellpadding="0" height="159">
<tr>
<td width="36%" height="176" valign="top"
align="center"><a target="_blank"
href="http://www.efficientsolution.com/shop_efsProd.asp?id=
1" ><img target="_blank"
src="http://www.efficientsolution.com/mailout/side2.gif"
width="178" height="135" border=0></a></td>
<td width="2%" height="176"> </td>
<td width="62%" valign="top" height="176"><br>
<table cellspacing=0 cellpadding=0 width="100%"
border=0>
<tbody>
<tr>
<td width="3%"> <img height=9 target="_blank"
src="http://www.efficientsolution.com/mailout/a.gif" width=8>
</td>
<td><font face="arial, Helvetica, sans-serif"><font
size="2">1GB of monthly transfer data rate</font></font></td>
</tr>
<tr>
<td width="3%"><img height=9 target="_blank"
src="http://www.efficientsolution.com/mailout/a.gif"
width=8></td>
<td><font face="arial, Helvetica, sans-serif"><font
size="2">100
MB of disk space (about 600 web pages)</font>
</font></td>
</tr>
<tr>
<td width="3%">
<img height=9 target="_blank"
src="http://www.efficientsolution.com/mailou
t/a.gif"
width=8></td>
<td><font
face="arial, Helvetica, sans-serif"><font size="2">~100,000
hits/month</font></font></td>
</tr>
<tr>
<td width="3%"> <img height=9 target="_blank"
src="http://www.efficientsolution.com/mailout/a.gif"
width=8></td>
<td><font face="Arial, Helvetica, sans-serif"><font
size="2">10 POP3/SMTP email accounts</font></font></td>
</tr>
<tr>
<td height=18 width="3%"><font
face="Arial, Helvetica, sans-serif"><b><font size=2>
<img target="_blank"
height=9
src="http://www.efficientsolution.com/mailout/a.gif"
width=8></font></b></font></td>
<td height=18><font
face="Arial, Helvetica, sans-serif"><font size=2>
24x7 FTP access</font></font><font
face="Arial, Helvetica, sans-serif"><font
size=2></font></font></td>
</tr>
</tbody>
</table>
<table width="100%" border="0" cellspacing="0"
cellpadding="0">
<tr>
<td width="46%">
<font face="Arial, Helvetica, sans-serif" size=2><u>
<a target="_blank"
href="http://www.efficientsolution.com/shop_efsProd.asp?id=
1"><fonT color=#B40403>Click for more info</font></A></u>
</font><br>
<font face="Arial, Helvetica, sans-serif" size=2><u>
<a target="_blank"
href="http://www.efficientsolution.com/submit.asp"><font
color=#B40403>Free submission form</font></a>
</u></font></td>
<td width="54%"><img target="_blank"
src="http://www.efficientsolution.com/mailout/ux.gif"
width="120" height="50"></td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td> </td>
</tr>
<tr>
<td><a target="_blank"
href="http://www.efficientsolution.com/shop_efsProd.asp?id=
3" ><img target="_blank"
src="http://www.efficientsolution.com/mailout/bot.gif"
width="500" height="54" border="0"></a></td>
</tr>
<tr>
<td height="1" bgcolor="#132A63"></td>
</tr>
</table>
<br>
<table width="70%" border="0" align=center><br><br><br>
<tr>
<td><font size="-1">You received this email because you
signed up at one
of Efficient Solution's websites or you signed up with a
party that
has contracted with Efficient Solution.To read Efficient
Solution's privacy
policy, visit Privacy
Policy. The products and/or services advertised in this
email are the
sole responsibility of the advertiser, and questions about
this offer
should be directed to the advertiser.<br>
© 2002 Efficient Solution, Inc. All rights reserved.
</font><br>
</td>
</tr>
</table>
<p> </p>
</div>
</body>
</html>
--__--__--
Message: 3
Date: Thu, 10 Oct 2002 09:09:10 +0200
From: Michael Salmon <Michael...@uab.ericsson.se>
To: rs...@lists.samba.org
Subject: Re: Value too large for defined data type
On Wednesday, October 09, 2002 07:26:44 AM -0700 Jeff.Le...@adic.com
wrote:
+------
| Howdy,
|
| I am just starting to use rsync and now have an rsync server set up
| to back up our various machines. I recently started getting an error that
| is confusing and I can't find info documented on it. I searched the news
| group and found it mentioned but no solution yet.
|
| I get the error when sync'ing from a Solaris 8 machine to my Solaris 8
| server.
|
| stat space/sunpci/drives/F.drive/docs/StorNext/LinuxPort/devfs.README.txt
| : Value too large for defined data type
| stat space/sunpci/drives/F.drive/docs/StorNext/StorNextNotes.doc : Value
| too large for defined data type
|
| I also see the same error going from our IRIX 6.5.15 machine, and the
| error is seen on a directory vs a file:
| stat apps1/fsdev.cliff/jleuschner/phoenix/ver_2.1.0B57/phtm/ver : Value
| too large for defined data type
| stat apps1/fsdev.cliff/jleuschner/phoenix/ver_2.1.0B57/phtm/ver/CVS :
| Value too large for defined data type
|
|
| Any ideas as to why this is occurring and what I can do to get around
| this? I appears that the file gets sync'd anyway. In addition the files
| vary in sizes, some of which do not appear to be too large.
+-----X8
It could be the times that are too large, particularly if NFS is involved.
NFS defines times as being 32 bit unsigned values but Unix time is a 32 bit
signed value and hence times before 1970 cannot be used in NFS.
/Michael
--
This space intentionally left non-blank.
--__--__--
Message: 4
From: "Moughan, Laurence" <Laurence...@o2.com>
To: "'rs...@lists.samba.org'" <rs...@lists.samba.org>
Subject: multiple sessions to same destination
Date: Thu, 10 Oct 2002 10:01:32 +0100
Hi All,
I had a look in archives but no joy.
I just want to know before i deploy - if there is any problem with having
multiple rsync sessions from many source locations all to same destination
server ( all copying to different file systems obviously ) ?? Its jusat that
i see on the destination machine a process rsync -server being called
whenever a client connects.
Thanks !
Laurence Moughan
OSS Engineer
O2 Ireland
76 Lower Baggot St,
Dublin 2,
Ireland
t +353 (1) 6095363
m +353 (0) 86 8142365
f +353 (1) 6195363
****************************************************************************
************
This E-mail is from O2. The E-mail and any files
transmitted with it are confidential and may also be privileged and intended
solely for the use of the individual or entity to whom they are addressed.
Any unauthorised direct or indirect dissemination, distribution or copying
of this message and any attachments is strictly prohibited. If you have
received the E-mail in error please notify postm...@O2.com or
telephone ++ 353 1 6095000.
****************************************************************************
*************
--__--__--
Message: 5
From: tim.c...@philips.com
To: Jeff.Le...@adic.com
Cc: rs...@lists.samba.org
Subject: Re: Value too large for defined data type
Date: Thu, 10 Oct 2002 06:33:47 -0700
Jeff: I found that problem in our Sun systems. It's commonly called the
mtime bug. Times are stored as a signed 32-bit integer. The high bit is
supposed to be disregarded by clients, and can be used for some purposes
by the OS. I think it's usually used for something called "exclusive
create". Anyway, we applied the patch on our solaris systems, and it
didn't go away. The way we got around it was to specify mounting via NFS2
instead of NFS3. If I misunderstand you, and it's not an NFS mount, sorry
for the irrelevance.
Tim Conway
conwa...@sphlihp.com reorder name and reverse domain
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me.... Tim?"
Jeff.Le...@adic.com
Sent by: rsync...@lists.samba.org
10/09/2002 08:26 AM
To: rs...@lists.samba.org
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: Value too large for defined data type
Classification:
Howdy,
I am just starting to use rsync and now have an rsync
server set up
to back up our
various machines. I recently started getting an error that is confusing
and
I can't find info
documented on it. I searched the news group and found it mentioned but no
solution yet.
I get the error when sync'ing from a Solaris 8 machine to my Solaris 8
server.
stat space/sunpci/drives/F.drive/docs/StorNext/LinuxPort/devfs.README.txt
:
Value too large for defined data type
stat space/sunpci/drives/F.drive/docs/StorNext/StorNextNotes.doc : Value
too
large for defined data type
I also see the same error going from our IRIX 6.5.15 machine, and the
error
is seen on a directory
vs a file:
stat apps1/fsdev.cliff/jleuschner/phoenix/ver_2.1.0B57/phtm/ver : Value
too
large for defined data type
stat apps1/fsdev.cliff/jleuschner/phoenix/ver_2.1.0B57/phtm/ver/CVS :
Value
too large for defined data type
Any ideas as to why this is occurring and what I can do to get around
this?
I appears that the
file gets sync'd anyway. In addition the files vary in sizes, some of
which
do not appear
to be too large.
Thanks,
Jeff
Jeff Leuschner
ADIC/Sr Software Engineer
972-669-4228
jeff.le...@adic.com
AOL IM: jeffleusch
http://www.adic.com
--
To unsubscribe or change options:
http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html