stat failed system error: Value too large for defined data type

unix

    Next

  • 1. basic networking: when to stop recv()ing?
    I've seen in some trials that if a client has a socket opened and a server calls recv() with a buffer which is greater than the number of bytes already sent recv() blocks. (I used several sends with sleeps() in between). Is there a standard way to know when you've got all the data albeit the socket is opened? -- fxn
  • 2. How to test if stdout == stderr?
    Hi! In a C program (Mac OSX Darwin/BSD), I'd like to check whether stdout and stderr are pointing to the same file. When stdout and stderr are pointing to a tty, I can do the following test: strcmp(ttyname(fileno(stderr)), ttyname(fileno(stdout))) == 0 But what if stdin and stderr have been both redirected to a file? How to test whether it is the same actual file or not? Thanks!
  • 3. TIOCOUTQ from Linux to Solaris
    I am porting a piece of code from Linux RH8 (g++ 3.2.2) to SunOS 5.8 (g++ 3.2). This fragment works on my tux box; on Solaris I obtain "No such file or directory". The socket is there; what's wrong with that? Any alternative to TIOCOUTQ on Solaris? Thanks Bye Giovanni bool User::isReceiving() { int remaining; int funit = sock->get_m_sock(); if (ioctl(funit, TIOCOUTQ, (char *) &remaining) < 0) { perror("<ERROR > ioctl\n"); } if (remaining != 0) LogRecord(LOG_DEBUG, "< DEBUG > User %s remaining %d\n", getID().c_str(), remaining); if (remaining > 0) return true; else return false; }
  • 4. Uniquely identifying disks in Unix.
    Problem: trying to (programmatically) find out if two disks (with no file system) seen from two different nodes are actually the same. We can't write on the disk. If there is a unique signature on each disk (like windows) then problem is solved, is there such a thing in the Disk Label? Would it work if I tried to get the SCSI serial ID + vendor name from the disk? Do I need to be root? Does it always work? I would really appreciate your help.

stat failed system error: Value too large for defined data type

Postby mobenoua » Fri, 20 Oct 2006 22:37:21 GMT

I am getting this message

stat failed system error: Value too large for defined data type

whilst trying to delete a binary file from my disk space using
the command remove from stdio in my c++ program. I am using solaris
2.8. Does anyone know the reason?

Thanks


Re: stat failed system error: Value too large for defined data type

Postby James Carlson » Sat, 21 Oct 2006 06:17:18 GMT

"mobenoua" < XXXX@XXXXX.COM > writes:

That typically means you're trying to open or stat a file that's
greater than 2GB in size, but your program isn't compiled or written
for large file support.

-- 
James Carlson, KISS Network                    < XXXX@XXXXX.COM >
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

Re: stat failed system error: Value too large for defined data type

Postby Mig21 » Sat, 21 Oct 2006 12:54:17 GMT

mobenoua a rit :

try this: 
 http://www.**--****.com/ #decafff67ce3a40c

Similar Threads:

1."Value too large for defined data type" error when using tar

Hi folks:

I receive this error when trying to extract tar files from disk, for
example:

   #tar xvf TARFILE.tar
    tar: Cannot open TARFILE.tar: Value too large for defined data
type

This only occurs with large files.  The files I have that are larger
than 3GB do not work, the next smallest are 1.5 GB, and those work. 
It appears it is not working for files larger than 2 gigabytes.

I am running Solaris 9 April/2003 release with the Dec 2003 patch
cluster, plus the 113072-07 patch.

I wish to send the tar files on a USB drive, since the recipient does
not have a DLT drive to tar them off of, so a DLT solution will not
work for this occassion.  A workaround would be to use winzip to
extract them, but will require significant work to restore them
correctly, since we use a specific script in conjunction with tar to
restore the files in a particular way.

If anyone is familiar with this and can offer a solution, that would
be great.

thanks much,
-Jeff

2.lseek: Value too large for defined data type

Hi All,

I have written 21GB file and updating the file by seeking 1K and
writing 100MB of data consecutively 10240 times. when after writing
2GB(2100 times) of file it was giving

lseek: Value too large for defined data type error.

What is got is the value passed to 'Offset' argument is too large to
handle.

The last return value of seek is '2099270656'

Is there any way to overcome this.


Thanks & Regads
Gururaja

3./dev/ppp: Value too large for defined data type

All,

I am having trouble with my PPTP connection. I have searched the
internet,
FAQ's, docs, looked though code, and tried different program options. I

basically exhausted those things I can think of and was wondering if
someone can help or suggest other ideas. (I did find some posts that
may
be related, but they were in a language I did not understand.)

I use a Linux based system (RH4 with new kernel) as a gateway between
the
internet and my local LAN. I use PPTP (w MPPE) to connect to a VPN
which
(with the right routing) gives me access to the VPN from any of the
machines on the LAN.

There is a limitation however that is manifesting itself as the error
in
the subject line. When I try to connect to an exchange server on the
VPN
from a Windows Outlook client on the LAN, I get the above error
and then pppd dies and needs to be restarted. I also noticed this
problem
when trying to access some web services on the VPN from the Windows
client.

The problem occurs from other Windows and Linux systems on the LAN as
well. The only time the problem did not occur was when I access the VPN
web resource from the gateway Linux, the same machine that created the
PPTP connection.

The connection works fine for all my other purposes.

The following command is how I initiate the connection to the VPN,
names
have been change to protect the innocent.

/usr/sbin/pptp vpn.example.com name domain\\joeuser remotename
vpn.example.comp require-mppe noauth unit 0

I attached some data related to my system to the end of the post.

According to the pppd log entry (below), the problem occurs in the
driver
read. So, when I look at the ppp_generic.c code I can see in the
ppp_read
method that -EOVERFLOW is returned if the size of the data read off the
device is larger then that which was requested in the read. The pppd
(sys-linux.c:read_packet) code that calls the read checks this return
value, reports it (the log entry) and then exits to the calling method.
I
am not sure what happens after that. I even played around with the mru
option on pppd after seeing this code, but it did not help.

By the way, this system is new and replacing and older one that ran
RH9. I
had the kernel-mppe package installed on the old system and it worked
fine.

I am not sure if this is a kernel issue or a pppd issue, so I
apologize if this is posted in the wrong place.

Thanks in advance for any help.

Tpf

The RH9 system had:
ppp-2.4.2-0.1b3
pptp-linux-1.3.1-1
kernel-mppe-2.4.20-18.9
kernel-2.4.20-18.9

The New system:

pppd.log entry
========
Mar 23 12:36:32 mail pppd[15970]: read /dev/ppp: Value too large for
defined data type

pptp version: pptp-linux-1.5.0-3

------ scripts/ver_linux ---------

If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux crow 2.6.15.6smp-1 #2 SMP Wed Mar 15 20:58:26 EST 2006 i686 i686
i386 GNU/ Linux

Gnu C                  3.4.5
Gnu make               3.80
binutils               2.15.92.0.2
util-linux             2.12a
mount                  2.12a
module-init-tools      3.1-pre5
e2fsprogs              1.35
reiserfsprogs          line
reiser4progs           line
pcmcia-cs              3.2.7
quota-tools            3.12.
PPP                    2.4.2
isdn4k-utils           3.3
nfs-utils              1.0.6
Linux C Library        2.3.4
Dynamic linker (ldd)   2.3.4
Procps                 3.2.3
Net-tools              1.60
Kbd                    1.12
Sh-utils               5.2.1
udev                   039
Modules Loaded         nfs lockd nls_utf8 loop ip_conntrack_ftp arc4
ppp_mppe pp p_async crc_ccitt ppp_generic slhc parport_pc lp parport
autofs4 sunrpc iptable_ nat ip_nat ipt_REJECT ipt_LOG ipt_state
ip_conntrack iptable_filter ip_tables ip v6 dm_mirror dm_mod button
battery ac uhci_hcd ehci_hcd shpchp hw_random i2c_i80 1 i2c_core
snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_tim
er
snd soundcore snd_page_alloc via_rhine e100 mii floppy ext3 jbd raid1
ata_pii x libata sd_mod scsi_mod

=======================================================
/proc/cpu_info
=======================================================
processor       :
0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 4
model name      : Intel(R) Pentium(R) D CPU 2.80GHz stepping        : 4
cpu MHz         : 2810.504
cache size      : 1024 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm pni
monitor ds_cpl cid cx16 xtpr
bogomips        : 5627.46

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 15
model           : 4
model name      : Intel(R) Pentium(R) D CPU 2.80GHz stepping        : 4
cpu MHz         : 2810.504
cache size      : 1024 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm pni
monitor ds_cpl cid cx16 xtpr
bogomips        : 5620.40

=======================================================
/proc/ioports
=======================================================

0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
0290-0297 : pnp 00:07
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial
0400-041f : 0000:00:1f.3
  0400-0407 : i801_smbus
0800-0803 : PM1a_EVT_BLK
0804-0805 : PM1a_CNT_BLK
0808-080b : PM_TMR
0810-0815 : ACPI CPU throttle
0820-0820 : PM2_CNT_BLK
0828-082f : GPE0_BLK
7000-701f : 0000:00:1d.0
  7000-701f : uhci_hcd
7400-741f : 0000:00:1d.1
  7400-741f : uhci_hcd
7800-781f : 0000:00:1d.2
  7800-781f : uhci_hcd
8000-801f : 0000:00:1d.3
  8000-801f : uhci_hcd
8400-840f : 0000:00:1f.2
  8400-840f : libata
8800-8803 : 0000:00:1f.2
  8800-8803 : libata
9000-9007 : 0000:00:1f.2
  9000-9007 : libata
9400-9403 : 0000:00:1f.2
  9400-9403 : libata
9800-9807 : 0000:00:1f.2
  9800-9807 : libata
a000-cfff : PCI Bus #01
  a800-a8ff : 0000:01:01.0
    a800-a8ff : via-rhine
  b000-b03f : 0000:01:02.0
    b000-b03f : e100
  b400-b40f : 0000:01:03.0
  b800-b803 : 0000:01:03.0
  c000-c007 : 0000:01:03.0
  c400-c403 : 0000:01:03.0
  c800-c807 : 0000:01:03.0
d000-dfff : PCI Bus #02
e000-efff : PCI Bus #03
  e000-e0ff : 0000:03:00.0
ffa0-ffaf : 0000:00:1f.1
  ffa0-ffa7 : ide0
  ffa8-ffaf : ide1
=======================================================
/proc/iomem
=======================================================

00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000d0000-000d0fff : Adapter ROM
000f0000-000fffff : System ROM
00100000-7ff9ffff : System RAM
  00100000-002e1d0a : Kernel code
  002e1d0b-003a89c3 : Kernel data
7ffa0000-7ffadfff : ACPI Tables
7ffae000-7ffdffff : ACPI Non-volatile Storage 7ffe0000-7fffffff :
reserved
88000000-881fffff : PCI Bus #01
  88000000-880fffff : 0000:01:02.0
  88100000-8811ffff : 0000:01:03.0
  88120000-8812ffff : 0000:01:01.0
d7bf8000-d7bfbfff : 0000:00:1b.0
  d7bf8000-d7bfbfff : ICH HD audio
d7bff800-d7bffbff : 0000:00:1d.7
  d7bff800-d7bffbff : ehci_hcd
d7bffc00-d7bfffff : 0000:00:1f.2
  d7bffc00-d7bfffff : libata
d7c00000-d7efffff : PCI Bus #01
  d7d00000-d7dfffff : 0000:01:02.0
    d7d00000-d7dfffff : e100
  d7edec00-d7edecff : 0000:01:01.0
    d7edec00-d7edecff : via-rhine
  d7edf000-d7edffff : 0000:01:02.0
    d7edf000-d7edffff : e100
d7f00000-d7ffffff : PCI Bus #03
  d7fc0000-d7fdffff : 0000:03:00.0
  d7fe0000-d7feffff : 0000:03:00.0
  d7ff0000-d7ffffff : 0000:03:00.1
d8000000-dfffffff : PCI Bus #03
  d8000000-dfffffff : 0000:03:00.0
ffb80000-ffffffff : reserved

=======================================================

4.Cannot access '/dev/pts/292': Value too large for defined data type

5.Cannot access '/dev/pts/292': Value too large for defined data type

6. Value too large for defined data type...

7. value too large for defined data type

8. UX:cpio: ERROR: Old format cannot support expanded types on {filename}: Value too large for defined data type



Return to unix

 

Who is online

Users browsing this forum: No registered users and 16 guest