On 10/17/2011 02:00 AM, Adam Yee wrote:
Dear developers and users,
The printed error message:
api-server: src/client/sysint/client-state-machine.c:862:
PINT_client_wait_internal: Assertion `smcb' failed.
/var/log/messages
Oct 16 22:54:29 server1 kernel: [ 3135.813404] api-server[10854]:
segfault at 0 ip 00007f591efbe6c2 sp 00007fff7f8f3990 error 4 in
libc-2.12.1.so <http://libc-2.12.1.so>[7f591ef84000+17a0 00]
Are you using the asynchronous interface (PVFS_isys_io() followed by
PVFS_sys_wait() or similar)? If so, it looks like an invalid op id
might have been passed into the latter. You might want to check and
make sure that PVFS_isys_io() didn't return an error code.
The above segfaults occur when the assertion fails.
I'm testing the write capabilities of orangefs-2.8.4 in the API I
built. I can successfully write 2GB, but when I try to write a larger
file, I consistently get the error above just after the 2GB mark.
Know any causes of this error type during a write? Is there a
configuration I have overlooked?
I haven't run into this in a while, but 2 GB is the limit of an offset
that is stored in a 32 bit integer. You might want to double check that
you are using a large enough integer for the offset, or that you are
using an off_t and compiling with large file support if you are on a 32
bit machine.
-Phil
Thanks,
Adam
_______________________________________________
Pvfs2-developers mailing list
Pvfs2-developers@beowulf-underground.org
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
_______________________________________________
Pvfs2-developers mailing list
Pvfs2-developers@beowulf-underground.org
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
