Did you have a chance to test the pvfs2-cp without replication enabled ( maybe on a local filesystem on one metadata server)? I'm just trying to isolate if the replication is the cause or another issue.
Maybe someone else on the list has seen this issue before? Michael On Feb 14, 2011, at 9:31 AM, jon jon <[email protected]> wrote: > Hi Michael, > > Yes i am trying to add high availability to the metadata servers using > Berkeley db if this is what u ask. > > -Yiannis > > --- Στις Δευτ., 14/02/11, ο/η Michael Moore <[email protected]> έγραψε: > > Από: Michael Moore <[email protected]> > Θέμα: Re: [Pvfs2-developers] pvfs2-cp.c returns segmentation fault > Προς: "jon jon" <[email protected]> > Κοιν.: "[email protected]" > <[email protected]> > Ημερομηνία: Δευτέρα, 14 Φεβρουάριος 2011, 16:25 > > Hi Yiannis, > > What do you mean by using replication? Is the underlying filesystem shared > between the two metadata servers? > > Michael > > On Feb 14, 2011, at 8:52 AM, jon jon <[email protected]> wrote: > >> hello all, >> >> I m using pvfs.2-8-1. I have 1 I/O server and 2 metadata servers using >> replication. I am on User mode. When i run pvfs2-cp it returns a >> segmentation fault. The file that i am trying to cp is copied successfully. >> After using gdb here is what i get: >> >> [Thread debugging using libthread_db enabled] >> [New Thread 0xb7ef56c0 (LWP 31833)] >> >> Program received signal SIGSEGV, Segmentation fault. >> io_inspect_attr (smcb=0x9aa6610, js_p=0xbfef0c58) at >> src/client/sysint/sys-io.sm:2926 >> >> backtrace returned: >> >> #0 io_inspect_attr (smcb=0x8f96ba8, js_p=0xbfe99f08) >> at src/client/sysint/sys-io.sm:2926 >> #1 0x08090433 in PINT_state_machine_invoke (smcb=0x8f96ba8, r=0xbfe99f08) >> at src/common/misc/state-machine-fns.c:132 >> #2 0x0809077d in PINT_state_machine_next (smcb=0x8f96ba8, r=0xbfe99f08) >> at src/common/misc/state-machine-fns.c:309 >> #3 0x08090301 in PINT_state_machine_continue (smcb=0x8f96ba8, r=0xbfe99f08) >> at src/common/misc/state-machine-fns.c:327 >> #4 0x08090391 in PINT_state_machine_start (smcb=0x8f96ba8, r=0xbfe99f08) >> at src/common/misc/state-machine-fns.c:202 >> 0x080577a7 in PINT_client_state_machine_post (smcb=0x8f96ba8, >> op_id=0xbfe99ff0, >> user_ptr=0x0) at src/client/sysint/client-state-machine.c:405 >> #6 0x080657fa in PVFS_isys_io (ref= >> {handle = 4611686018427386622, fs_id = 1938003253, __pad1 = 0}, >> file_req=0x80c8ec0, file_req_offset=0, buffer=0xb75cc008, >> mem_req=0x8f96968, >> credentials=0xbfe9a5ec, resp_p=0xbfe9a5e4, io_type=PVFS_IO_READ, >> op_id=0xbfe99ff0, >> hints=0x0, user_ptr=0x0) at src/client/sysint/sys-io.sm:346 >> #7 0x0806598c in PVFS_sys_io (ref= >> {handle = 4611686018427386622, fs_id = 1938003253, __pad1 = 0}, >> file_req=0x80c8ec0, file_req_offset=0, buffer=0xb75cc008, >> mem_req=0x8f96968, >> credentials=0xbfe9a5ec, resp_p=0xbfe9a5e4, io_type=PVFS_IO_READ, >> hints=0x0) >> at src/client/sysint/sys-io.sm:370 >> #8 0x0805365a in main (argc=Cannot access memory at address 0x0 >> ) at src/apps/admin/pvfs2-cp.c:340 >> >> >> It get a segfault in file sys-io.sm, function :unstuff_needed >> when trying to execute: >> first_unstuffed_offset = dist_p->methods->next_mapped_offset( >> dist_p->params, >> &fake_file_data, >> 0); >> >> >> Any help or information about what is causing this would be great. >> >> -Yiannis >> >> _______________________________________________ >> Pvfs2-developers mailing list >> [email protected] >> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers >
_______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
