[PVFS2-developers] Determining meaning of error code on I/O
Dean Hildebrand
dhildebz at eecs.umich.edu
Mon Jul 12 20:08:50 EDT 2004
Hello,
I've hacked up PVFS2 quite a bit now for my pNFS work and I'm receiving an
error in io_datafile_complete_msgpairs when submitting a write request
(similar with read).
The full trace is below, but the main lines are:
all msgpairs complete.
matched response from 0.
error 0 with status -1073741828 related to response from 0; not
submitting flow.
Can anyone tell me what error -1073741828 means (-0x40000004)? The first
time I write to a new file it works fine, but the second time I get this
error. I can't seem to find this error in a table anywhere. It is always
the same error though, so I don't think it is just garbage.
Thanks,
Dean
ps: The trace may look a little wierd since I'm not getting the file
attributes directly from the PVFS2 server, but instead injecting them from
the NFSv4 client.
PVFS_sys_io entered
PVFS_isys_io entered
PVFS_isys_io fsid:925967295 handle:2147483649
io state: init
PINT_sm_common_object_getattr_setup_msgpair
setup fsid:925967295 handle:2147483649
getattr_acache state: lookup
getattr_acache state: fs_id:925967295 handle:2147483649
PINT_acache_lookup entered
PINT_acache_lookup exiting
getattr_acache state: Found!
PINT_acache_status called
pinode_status entered
PINODE STATUS IS PINODE STATUS VALID
pinode_status exited
getattr_acache state: Valid!
acache: acache hit
PINT_sm_common_getattr_object_comp_fn
PINT_acache_release entered
PINT_acache_release exited
(0x80c2b08) io state: io_datafile_setup_msgpairs
Searching for dist simple_stripe
PINT_New_request_state
PINT_New_request_state
PINT_Process_request
size request - copying state, hold on to your hat! dp 1
tiling 8 copies
Do seq of 0 ne 1 st 1 nb 0 ub 1 lb 0 as 1 co 0
lvl 0 el 0 blk 0 by 0
to 0 ta 0 fi 7
basic type or contiguous data
calling distribute
PINT_Distribute
of 0 sz 7 ix 0 sm 1 by 0 bm 1 fsz 0 exfl 1
begin iteration loff: 0
segment exceeds byte limit
file being extended
process a segment
of 0 sz 1
count segment in checksize
end iteration
done with segments or bytes
finished
of 1 sz 6 sg 1 sm 1 by 1 bm 1
next loff: 1 next poff: 1
return value 1
exiting distribute returned less than expected
done sg 1 sm 1 by 1 bm 1 ta 0 to 1 fo 7 eof 0
tiling 8 copies
Do seq of 0 ne 1 st 1 nb 0 ub 1 lb 0 as 1 co 0
lvl 0 el 0 blk 0 by 0
to 0 ta 0 fi 7
basic type or contiguous data
calling distribute
PINT_Distribute
of 0 sz 7 ix 0 sm 1 by 0 bm 1 fsz 0 exfl 1
begin iteration loff: 0
segment exceeds byte limit
file being extended
segment exceeds byte limit
file being extended
process a segment
of 0 sz 1
count segment in checksize
end iteration
done with segments or bytes
finished
of 1 sz 6 sg 1 sm 1 by 1 bm 1
next loff: 1 next poff: 1
return value 1
exiting distribute returned less than expected
done sg 1 sm 1 by 1 bm 1 ta 0 to 1 fo 7 eof 0
io_find_target_dfiles: datafile 0 might have some data.
datafile_setup_msgpairs: 1 datafiles might have data
sending I/O request for 135047520
io_datafile_post_msgpairs state: post (1 message(s))
PINT_Do_Request_commit: commit node 0x809a6c0
node stored at 0
clearing tree
io_datafile_post_msgpairs: send completed immediately.
PVFS_isys_io calling PINT_client_state_machine_test()
REQ SCHED SCHEDULING, queue_element: 0x80c2500
REQ SCHED POSTING, queue_element: 0x80c2500
PVFS_isys_io calling PINT_client_state_machine_test()
io state: datafile_complete_msgpairs
all msgpairs complete.
matched response from 0.
error 0 with status -1073741828 related to response from 0; not
submitting flow.
io state: datafile_complete_msgpairs
trying to match to a flow or ack.
all msgpairs, flows, ack completed.
(0x80c2b08) io state: analyze_results
More information about the PVFS2-developers
mailing list