Value too large for defined data type
Jeff.Le...@adic.com
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
jw schultz
> 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
Michael Salmon
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
|
|
| 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.
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.
tim.c...@philips.com
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,
Thanks,
Jeff
Jeff Leuschner
ADIC/Sr Software Engineer
972-669-4228
jeff.le...@adic.com
AOL IM: jeffleusch
http://www.adic.com
--
David Bigagli -Bokis-
Would it help to build with SunPro cc compiler using the -xarch=v9
option? This will build a native 64 bit binary.
Cheers,
David
On Wed, 9 Oct 2002, jw schultz wrote:
> 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
jw schultz
>
> Would it help to build with SunPro cc compiler using the -xarch=v9
> option? This will build a native 64 bit binary.
Not likely. If i correctly diagnosed his problem it is the
syscall/library interface and datatypes. That is correctable
by a build option.
It should be noted that very few sites even have the SunPro
compiler. Having correct binaries depend on the proprietary,
and overpriced, compiler would exclude most potential users.
David Bigagli -Bokis-
> Not likely. If i correctly diagnosed his problem it is the
> syscall/library interface and datatypes. That is correctable
> by a build option.
Sure, but this build option probably declares the data types to be the
same size as if you compile in native 64 bit mode.
David