[PVFS-users] nonlocal communication fails (was Re: your mail)
Natalie Protasevich
protasnb@yahoo.com
Tue, 15 Jul 2003 14:51:47 -0700 (PDT)
--0-1287780341-1058305907=:52786
Content-Type: text/plain; charset=us-ascii
Rob,
Thanks for your prompt response.
I am not familiar with pvfs code, so I am moving in the dark so far.
Before I carefully digest your response, given the chance I'd like to have you
take a look at the rest of the data, maybe this will dive you a better picture.
What you said about sockets... I checked active connections
and the client side doesn't look very good.
(I have to mention that the systems are handling multiple NFS shares,
run numerous MPI enabled tests and benchmarks, etc.)
Here is some connection information on the server (its IP addr ends with 103, client's side ends with 104):
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.2:3000 127.0.0.2:32785 ESTABLISHED
tcp 0 0 127.0.0.2:32785 127.0.0.2:3000 ESTABLISHED
tcp 0 0 127.0.0.2:7000 127.0.0.2:32807 ESTABLISHED
tcp 0 0 127.0.0.2:7000 127.0.0.2:32935 ESTABLISHED
tcp 0 0 127.0.0.2:32935 127.0.0.2:7000 ESTABLISHED
tcp 0 0 127.0.0.2:32807 127.0.0.2:7000 ESTABLISHED
tcp 0 0 192.168.1.103:32820 192.168.1.104:22 ESTABLISHED
tcp 0 0 192.168.1.103:32936 192.168.1.104:7000 ESTABLISHED
tcp 0 0 192.168.1.103:32934 192.168.1.104:7000 ESTABLISHED
tcp 0 0 192.168.1.103:3000 192.168.1.104:33259 ESTABLISHED
tcp 0 0 192.60.139.225:22 192.60.131.148:3283 ESTABLISHED
tcp 0 0 192.60.139.225:22 192.60.131.148:3282 ESTABLISHED
tcp 0 0 192.60.139.225:22 192.60.129.123:1271 ESTABLISHED
tcp 0 0 192.60.139.225:22 192.60.129.123:1724 ESTABLISHED
And the client side looks worse (my iod process on the server died once, I had to restart it):
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 192.168.1.104:7000 192.168.1.104:33424 ESTABLISHED
tcp 0 0 127.0.0.2:7000 127.0.0.2:33418 TIME_WAIT
tcp 0 0 127.0.0.2:7000 127.0.0.2:33423 ESTABLISHED
tcp 0 0 192.60.137.229:33396 192.60.137.229:22 TIME_WAIT
tcp 0 0 192.60.137.229:33397 192.60.137.229:22 ESTABLISHED
tcp 0 0 192.60.137.229:33395 192.60.137.229:22 ESTABLISHED
tcp 0 0 127.0.0.2:33414 127.0.0.2:7000 TIME_WAIT
tcp 0 0 192.168.1.104:33417 192.168.1.104:7000 TIME_WAIT
tcp 0 0 127.0.0.2:33423 127.0.0.2:7000 ESTABLISHED
tcp 0 0 192.168.1.104:33422 192.168.1.104:7000 TIME_WAIT
tcp 0 0 192.168.1.104:33424 192.168.1.104:7000 ESTABLISHED
tcp 0 0 192.168.1.104:33259 192.168.1.103:3000 ESTABLISHED
tcp 0 0 192.168.1.104:7000 192.168.1.103:32934 ESTABLISHED
tcp 0 0 192.168.1.104:7000 192.168.1.103:32936 ESTABLISHED
tcp 0 0 192.60.137.229:835 192.60.129.49:32773 TIME_WAIT
tcp 0 0 192.60.137.229:838 192.60.129.49:32773 TIME_WAIT
tcp 0 0 192.60.137.229:22 192.60.137.229:33395 ESTABLISHED
tcp 0 0 192.60.137.229:22 192.60.137.229:33397 ESTABLISHED
tcp 0 0 192.168.1.104:22 192.168.1.100:33071 ESTABLISHED
tcp 0 0 192.168.1.104:22 192.168.1.100:33065 ESTABLISHED
tcp 0 0 192.168.1.104:22 192.168.1.100:33066 ESTABLISHED
tcp 0 0 192.168.1.104:22 192.168.1.103:32820 ESTABLISHED
tcp 0 0 192.168.1.104:22 192.168.1.103:32947 ESTABLISHED
tcp 0 0 192.60.137.229:22 192.60.131.148:4684 ESTABLISHED
Finally, this is the verbose output with high debug level which I unfortunately
cannot make sense of myself at this point:
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 91.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 91.
Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 92.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 92.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for test.
Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 93.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 93.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for test.
Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 94.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 94.
Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp
Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 95.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 95.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swp.
Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.
Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp
Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 96.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 96.
Jul 14 16:43:20 le104 kernel: (file.c, 520): pvfs_file_create called for 306038
Jul 14 16:43:20 le104 kernel: (file.c, 553): pvfs_file_create calling ll_pvfs_create
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 216): ll_pvfs_create called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 97.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 97.
Jul 14 16:43:20 le104 kernel: (file.c, 565): pvfs_file_create calling ll_pvfs_lookup
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 98.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 98.
Jul 14 16:43:20 le104 kernel: (inode.c, 230): pvfs_read_inode() called (does nothing).
Jul 14 16:43:20 le104 kernel: (file.c, 593): pvfs_file_create: saved name is 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swpx
Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swpx
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swpx
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 99.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 99.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swpx.
Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.
Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swpx
Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swpx
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swpx
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 100.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 100.
Jul 14 16:43:20 le104 kernel: (file.c, 520): pvfs_file_create called for 306038
Jul 14 16:43:20 le104 kernel: (file.c, 553): pvfs_file_create calling ll_pvfs_create
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 216): ll_pvfs_create called for 192.168.1.103:3000/pvfs-meta/.test.swpx
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 101.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 101.
Jul 14 16:43:20 le104 kernel: (file.c, 565): pvfs_file_create calling ll_pvfs_lookup
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swpx
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 102.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 102.
Jul 14 16:43:20 le104 kernel: (inode.c, 230): pvfs_read_inode() called (does nothing).
Jul 14 16:43:20 le104 kernel: (file.c, 593): pvfs_file_create: saved name is 192.168.1.103:3000/pvfs-meta/.test.swpx
Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swp (308049).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308049
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 103.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 103.
Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swpx (308059).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308059
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 104.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 104.
Jul 14 16:43:20 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/.test.swpx (308059)
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/.test.swpx
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): (pvfsdev.c, 762): pvfsdev: reading upcall number -1.
Jul 14 16:43:20 le104 kernel: pvfs_dentry_revalidate called for .test.swpx.
Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swpx (308059).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308059
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 105.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 105.
Jul 14 16:43:20 le104 kernel: (dir.c, 329): pvfs_unlink called on 306038 for .test.swpx
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 283): ll_pvfs_unlink called for 308059
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 106.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 106.
Jul 14 16:43:20 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/.test.swp (308049)
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (dir.c, 801): (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number -1.
Jul 14 16:43:20 le104 kernel: pvfs_dentry_revalidate called for .test.swp.
Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swp (308049).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308049
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 107.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 107.
Jul 14 16:43:20 le104 kernel: (dir.c, 329): pvfs_unlink called on 306038 for .test.swp
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 283): ll_pvfs_unlink called for 308049
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 108.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 108.
Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp
Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 109.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 109.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swp.
Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.
Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp
Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 110.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 110.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swp.
Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.
Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp
Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 111.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 111.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swp.
Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.
Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp
Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 112.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 112.
Jul 14 16:43:20 le104 kernel: (file.c, 520): pvfs_file_create called for 306038
Jul 14 16:43:20 le104 kernel: (file.c, 553): pvfs_file_create calling ll_pvfs_create
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 216): ll_pvfs_create called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 113.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 113.
Jul 14 16:43:20 le104 kernel: (file.c, 565): pvfs_file_create calling ll_pvfs_lookup
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 114.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 114.
Jul 14 16:43:20 le104 kernel: (inode.c, 230): pvfs_read_inode() called (does nothing).
Jul 14 16:43:20 le104 kernel: (file.c, 593): pvfs_file_create: saved name is 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (file.c, 366): pvfs_file_write called for 192.168.1.103:3000/pvfs-meta/.test.swp (308059), offset 0, size 4096
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 536): ll_pvfs_file_write called for 192.168.1.103:3000/pvfs-meta/.test.swp (308059), size 4096, loc 0
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 115.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 115.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 549): pvfsdev: performing memory xfer (write).
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 567): pvfsdev: preparing to copy 4096 bytes.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 115.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 549): pvfsdev: performing memory xfer (write).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 559): ll_pvfs_file_write got error in downcall
Jul 14 16:43:20 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/.test.swp (308059)
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/.test.swp
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): (pvfsdev.c, 762): pvfsdev: reading upcall number -1.
Jul 14 16:43:20 le104 kernel: pvfs_dentry_revalidate called for .test.swp.
Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swp (308059).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308059
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 116.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 116.
Jul 14 16:43:20 le104 kernel: (dir.c, 329): pvfs_unlink called on 306038 for .test.swp
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 283): ll_pvfs_unlink called for 308059
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 117.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 117.
Jul 14 16:43:20 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/test (308050)
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/test
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number -1.
Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for test.
Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).
Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 118.
Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 118.
Jul 14 16:43:21 le104 kernel: (file.c, 301): pvfs_file_read called for 192.168.1.103:3000/pvfs-meta/test (308050), offset 0, size 8192
Jul 14 16:43:21 le104 kernel: (ll_pvfs.c, 487): ll_pvfs_file_read called for 192.168.1.103:3000/pvfs-meta/test (308050), size 8192, loc 0
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 119.
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 119.
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 596): pvfsdev: performing memory xfer (read).
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 603): pvfsdev: preparing to copy 0 bytes.
Jul 14 16:43:21 le104 kernel: (ll_pvfs.c, 511): ll_pvfs_file_read got error in downcall
Jul 14 16:43:21 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/test (308050)
Jul 14 16:43:21 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/test
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number -1.
Jul 14 16:43:21 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for test.
Jul 14 16:43:21 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).
Jul 14 16:43:21 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 120.
Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 120.
Jul 14 16:43:21 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test
Rob Ross <rross@mcs.anl.gov> wrote:Hi Natalie,
This is very weird. So everything is ok mounted on the local machine, but
not across a wire?
Looks like you're using 1.5.8. There is a newer version, and it would be
great to have you using that version, but I don't think that this is a
problem that is fixed between the two.
On Tue, 15 Jul 2003, Natalie Protasevich wrote:
> Hi,
> I am installing PVFS on our cluster running SuSE Linux on IA64. I
> stumbled on the very first step here and would appreciate some help.
> Everything seems to work on the single host, but when I add a client on
> the other node, I cannot read/write to a file on the mounted PVFS
> partition. I can pvstat the file, pvfs-statfs works OK, but when I "cat"
> or "vi" the file, I get "write error in swap file" in vi. Here are
> outputs from various logs:
>
> pvfsdlog:
[snip]
> do_job: IOD_MAJIK_NR does not match
[snip]
This indicates that the pvfsd received something back from an iod with an
irregular iod_majik_nr field. This usually means that the entire message
is garbage.
Actually, this one I can explain; I'll get to it in a second.
> iolog:
>
> $Header: /projects/cvsroot/pvfs/iod/iod.c,v 1.60 2003/04/23 12:18:58 rbross Exp $
>
> new_request: close failed
>
> do_rw_req: empty job - removing
>
> new_request: invalid magic number; ignoring request.
>
> *** SENDING ERROR ***
[snip]
Likewise the iod saw a garbage request. The close request messages are a
little strange, but maybe that was local traffic? Hard to tell.
Anyway, when the iod sees a garbage request, it sends an error response
and then drops the connection. However, there's a bug in that code -- we
don't fill in the ack before sending it (just noticed this). So that's
why the pvfsd gets the message you see there. We'll need to fix this.
However, I still have no idea why the iod is seeing this garbage message
in the first place!
> Also, in /var/log/messages I always see the following:
>
> Jul 15 11:09:01 le104 kernel: pvfs: debug = 0x0, maxsz = 16777216 bytes, buffer = dynamic, major = 0
>
> Jul 15 11:09:48 le104 kernel: (ll_pvfs.c, 559): ll_pvfs_file_write got error in downcall
[snip]
This simply indicates that the pvfsd returned an error back to the kernel.
This is what we would expect given what we're seeing in the pvfsd log and
iod log.
> It looks like I am missing something, or it is some sort of timing
> issue. I have an output from the higher debug level, too, if someone
> will be willing to take a look.
>
> I will be trying to debug this problem but if someone have seen this or
> knows where to look for solution, I will appreciate some help.
I haven't seen this before. What type of interconnect are we talking
about here? Is there anything you can think of that would get extra data
into the sockets? I don't think that a misconfiguration would lead to
this particular behavior.
Rob
_______________________________________________
PVFS-users mailing list
PVFS-users@www.beowulf-underground.org
http://beowulf-underground.org/mailman/listinfo/pvfs-users
---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
--0-1287780341-1058305907=:52786
Content-Type: text/html; charset=us-ascii
<DIV><FONT size=2>
<P>Rob,</P>
<P> </P>
<P>Thanks for your prompt response.</P>
<P>I am not familiar with pvfs code, so I am moving in the dark so far. </P>
<P>Before I carefully digest your response, given the chance I'd like to have you </P>
<P>take a look at the rest of the data, maybe this will dive you a better picture.</P>
<P>What you said about sockets... I checked active connections </P>
<P>and the client side doesn't look very good. </P>
<P>(I have to mention that the systems are handling multiple NFS shares, </P>
<P>run numerous MPI enabled tests and benchmarks, etc.) </P>
<P> </P>
<P>Here is some connection information on the server (its IP addr ends with 103, client's side ends with 104):</P><FONT size=2>
<P>Active Internet connections (w/o servers)</P>
<P>Proto Recv-Q Send-Q Local Address Foreign Address State </P>
<P>tcp 0 0 127.0.0.2:3000 127.0.0.2:32785 ESTABLISHED </P>
<P>tcp 0 0 127.0.0.2:32785 127.0.0.2:3000 ESTABLISHED </P>
<P>tcp 0 0 127.0.0.2:7000 127.0.0.2:32807 ESTABLISHED </P>
<P>tcp 0 0 127.0.0.2:7000 127.0.0.2:32935 ESTABLISHED </P>
<P>tcp 0 0 127.0.0.2:32935 127.0.0.2:7000 ESTABLISHED </P>
<P>tcp 0 0 127.0.0.2:32807 127.0.0.2:7000 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.103:32820 192.168.1.104:22 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.103:32936 192.168.1.104:7000 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.103:32934 192.168.1.104:7000 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.103:3000 192.168.1.104:33259 ESTABLISHED </P>
<P>tcp 0 0 192.60.139.225:22 192.60.131.148:3283 ESTABLISHED </P>
<P>tcp 0 0 192.60.139.225:22 192.60.131.148:3282 ESTABLISHED </P>
<P>tcp 0 0 192.60.139.225:22 192.60.129.123:1271 ESTABLISHED </P>
<P>tcp 0 0 192.60.139.225:22 192.60.129.123:1724 ESTABLISHED </P></FONT>
<P> </P>
<P> </P>
<P>And the client side looks worse (my iod process on the server died once, I had to restart it):</P><FONT size=2>
<P>Active Internet connections (w/o servers)</P>
<P>Proto Recv-Q Send-Q Local Address Foreign Address State </P>
<P>tcp 0 0 192.168.1.104:7000 192.168.1.104:33424 ESTABLISHED </P>
<P>tcp 0 0 127.0.0.2:7000 127.0.0.2:33418 TIME_WAIT </P>
<P>tcp 0 0 127.0.0.2:7000 127.0.0.2:33423 ESTABLISHED </P>
<P>tcp 0 0 192.60.137.229:33396 192.60.137.229:22 TIME_WAIT </P>
<P>tcp 0 0 192.60.137.229:33397 192.60.137.229:22 ESTABLISHED </P>
<P>tcp 0 0 192.60.137.229:33395 192.60.137.229:22 ESTABLISHED </P>
<P>tcp 0 0 127.0.0.2:33414 127.0.0.2:7000 TIME_WAIT </P>
<P>tcp 0 0 192.168.1.104:33417 192.168.1.104:7000 TIME_WAIT </P>
<P>tcp 0 0 127.0.0.2:33423 127.0.0.2:7000 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.104:33422 192.168.1.104:7000 TIME_WAIT </P>
<P>tcp 0 0 192.168.1.104:33424 192.168.1.104:7000 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.104:33259 192.168.1.103:3000 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.104:7000 192.168.1.103:32934 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.104:7000 192.168.1.103:32936 ESTABLISHED </P>
<P>tcp 0 0 192.60.137.229:835 192.60.129.49:32773 TIME_WAIT </P>
<P>tcp 0 0 192.60.137.229:838 192.60.129.49:32773 TIME_WAIT </P>
<P>tcp 0 0 192.60.137.229:22 192.60.137.229:33395 ESTABLISHED </P>
<P>tcp 0 0 192.60.137.229:22 192.60.137.229:33397 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.104:22 192.168.1.100:33071 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.104:22 192.168.1.100:33065 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.104:22 192.168.1.100:33066 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.104:22 192.168.1.103:32820 ESTABLISHED </P>
<P>tcp 0 0 192.168.1.104:22 192.168.1.103:32947 ESTABLISHED </P>
<P>tcp 0 0 192.60.137.229:22 192.60.131.148:4684 ESTABLISHED </P></FONT>
<P> </P>
<P> </P>
<P>Finally, this is the verbose output with high debug level which I unfortunately </P>
<P>cannot make sense of myself at this point:</P>
<P> </P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 91.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 91.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 92.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 92.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for test.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 93.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 93.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for test.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 94.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 94.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 95.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 95.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swp.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 96.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 96.</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 520): pvfs_file_create called for 306038</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 553): pvfs_file_create calling ll_pvfs_create</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 216): ll_pvfs_create called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 97.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 97.</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 565): pvfs_file_create calling ll_pvfs_lookup</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 98.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 98.</P>
<P>Jul 14 16:43:20 le104 kernel: (inode.c, 230): pvfs_read_inode() called (does nothing).</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 593): pvfs_file_create: saved name is 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 99.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 99.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swpx.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 100.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 100.</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 520): pvfs_file_create called for 306038</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 553): pvfs_file_create calling ll_pvfs_create</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 216): ll_pvfs_create called for 192.168.1.103:3000/pvfs-meta/.test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 101.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 101.</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 565): pvfs_file_create calling ll_pvfs_lookup</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 102.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 102.</P>
<P>Jul 14 16:43:20 le104 kernel: (inode.c, 230): pvfs_read_inode() called (does nothing).</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 593): pvfs_file_create: saved name is 192.168.1.103:3000/pvfs-meta/.test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swp (308049).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308049</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 103.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 103.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swpx (308059).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308059</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 104.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 104.</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/.test.swpx (308059)</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/.test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): (pvfsdev.c, 762): pvfsdev: reading upcall number -1.</P>
<P>Jul 14 16:43:20 le104 kernel: pvfs_dentry_revalidate called for .test.swpx.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swpx (308059).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308059</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 105.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 105.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 329): pvfs_unlink called on 306038 for .test.swpx</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 283): ll_pvfs_unlink called for 308059</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 106.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 106.</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/.test.swp (308049)</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number -1.</P>
<P>Jul 14 16:43:20 le104 kernel: pvfs_dentry_revalidate called for .test.swp.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swp (308049).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308049</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 107.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 107.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 329): pvfs_unlink called on 306038 for .test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 283): ll_pvfs_unlink called for 308049</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 108.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 108.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 109.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 109.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swp.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 110.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 110.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swp.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 111.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 111.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for .test.swp.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 805): pvfs_dentry_revalidate: NULL inode (negative dentry) hit.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 112): pvfs_lookup called on 306038 for .test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 115): name might be 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 112.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 112.</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 520): pvfs_file_create called for 306038</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 553): pvfs_file_create calling ll_pvfs_create</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 216): ll_pvfs_create called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 113.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 113.</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 565): pvfs_file_create calling ll_pvfs_lookup</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 77): ll_pvfs_lookup called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 114.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 114.</P>
<P>Jul 14 16:43:20 le104 kernel: (inode.c, 230): pvfs_read_inode() called (does nothing).</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 593): pvfs_file_create: saved name is 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 366): pvfs_file_write called for 192.168.1.103:3000/pvfs-meta/.test.swp (308059), offset 0, size 4096</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 536): ll_pvfs_file_write called for 192.168.1.103:3000/pvfs-meta/.test.swp (308059), size 4096, loc 0</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 115.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 115.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 549): pvfsdev: performing memory xfer (write).</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 567): pvfsdev: preparing to copy 4096 bytes.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 115.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 549): pvfsdev: performing memory xfer (write).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 559): ll_pvfs_file_write got error in downcall</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/.test.swp (308059)</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/.test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): (pvfsdev.c, 762): pvfsdev: reading upcall number -1.</P>
<P>Jul 14 16:43:20 le104 kernel: pvfs_dentry_revalidate called for .test.swp.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/.test.swp (308059).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308059</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 116.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 116.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 329): pvfs_unlink called on 306038 for .test.swp</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 283): ll_pvfs_unlink called for 308059</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 117.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 117.</P>
<P>Jul 14 16:43:20 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/test (308050)</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/test</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number -1.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for test.</P>
<P>Jul 14 16:43:20 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).</P>
<P>Jul 14 16:43:20 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 118.</P>
<P>Jul 14 16:43:20 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 118.</P>
<P>Jul 14 16:43:21 le104 kernel: (file.c, 301): pvfs_file_read called for 192.168.1.103:3000/pvfs-meta/test (308050), offset 0, size 8192</P>
<P>Jul 14 16:43:21 le104 kernel: (ll_pvfs.c, 487): ll_pvfs_file_read called for 192.168.1.103:3000/pvfs-meta/test (308050), size 8192, loc 0</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 119.</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 119.</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 596): pvfsdev: performing memory xfer (read).</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 603): pvfsdev: preparing to copy 0 bytes.</P>
<P>Jul 14 16:43:21 le104 kernel: (ll_pvfs.c, 511): ll_pvfs_file_read got error in downcall</P>
<P>Jul 14 16:43:21 le104 kernel: (file.c, 426): pvfs_release called for 192.168.1.103:3000/pvfs-meta/test (308050)</P>
<P>Jul 14 16:43:21 le104 kernel: (ll_pvfs.c, 118): ll_pvfs_hint called for 192.168.1.103:3000/pvfs-meta/test</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number -1.</P>
<P>Jul 14 16:43:21 le104 kernel: (dir.c, 801): pvfs_dentry_revalidate called for test.</P>
<P>Jul 14 16:43:21 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test (308050).</P>
<P>Jul 14 16:43:21 le104 kernel: (ll_pvfs.c, 352): ll_pvfs_getmeta called for 308050</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 717): pvfsdev: someone is reading from me.</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 762): pvfsdev: reading upcall number 120.</P>
<P>Jul 14 16:43:21 le104 kernel: (pvfsdev.c, 488): pvfsdev: writing downcall number 120.</P>
<P>Jul 14 16:43:21 le104 kernel: (dir.c, 734): pvfs_revalidate_inode called for 192.168.1.103:3000/pvfs-meta/test </P></FONT><BR><BR><B><I>Rob Ross <rross@mcs.anl.gov></I></B> wrote:
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid; WIDTH: 100%">Hi Natalie,<BR><BR>This is very weird. So everything is ok mounted on the local machine, but <BR>not across a wire?<BR><BR>Looks like you're using 1.5.8. There is a newer version, and it would be <BR>great to have you using that version, but I don't think that this is a <BR>problem that is fixed between the two.<BR><BR>On Tue, 15 Jul 2003, Natalie Protasevich wrote:<BR><BR>> Hi,<BR>> I am installing PVFS on our cluster running SuSE Linux on IA64. I<BR>> stumbled on the very first step here and would appreciate some help.<BR>> Everything seems to work on the single host, but when I add a client on<BR>> the other node, I cannot read/write to a file on the mounted PVFS<BR>> partition. I can pvstat the file, pvfs-statfs works OK, but when I "cat"<BR>> or "vi" the file, I get "write error in swap file" in vi. Here are<BR>> outputs from various logs:<BR>> <BR>>
pvfsdlog:<BR><BR>[snip]<BR><BR>> do_job: IOD_MAJIK_NR does not match<BR><BR>[snip]<BR><BR>This indicates that the pvfsd received something back from an iod with an <BR>irregular iod_majik_nr field. This usually means that the entire message <BR>is garbage.<BR><BR>Actually, this one I can explain; I'll get to it in a second.<BR><BR>> iolog:<BR>> <BR>> $Header: /projects/cvsroot/pvfs/iod/iod.c,v 1.60 2003/04/23 12:18:58 rbross Exp $<BR>> <BR>> new_request: close failed<BR>> <BR>> do_rw_req: empty job - removing<BR>> <BR>> new_request: invalid magic number; ignoring request.<BR>> <BR>> *** SENDING ERROR ***<BR><BR>[snip]<BR><BR>Likewise the iod saw a garbage request. The close request messages are a <BR>little strange, but maybe that was local traffic? Hard to tell.<BR><BR>Anyway, when the iod sees a garbage request, it sends an error response <BR>and then drops the connection. However, there's a bug in that code -- we <BR>don't fill in the ack
before sending it (just noticed this). So that's <BR>why the pvfsd gets the message you see there. We'll need to fix this.<BR><BR>However, I still have no idea why the iod is seeing this garbage message <BR>in the first place!<BR><BR>> Also, in /var/log/messages I always see the following:<BR>> <BR>> Jul 15 11:09:01 le104 kernel: pvfs: debug = 0x0, maxsz = 16777216 bytes, buffer = dynamic, major = 0<BR>> <BR>> Jul 15 11:09:48 le104 kernel: (ll_pvfs.c, 559): ll_pvfs_file_write got error in downcall<BR><BR>[snip]<BR><BR>This simply indicates that the pvfsd returned an error back to the kernel. <BR>This is what we would expect given what we're seeing in the pvfsd log and <BR>iod log.<BR><BR>> It looks like I am missing something, or it is some sort of timing<BR>> issue. I have an output from the higher debug level, too, if someone<BR>> will be willing to take a look.<BR>> <BR>> I will be trying to debug this problem but if someone have seen this or<BR>>
knows where to look for solution, I will appreciate some help.<BR><BR>I haven't seen this before. What type of interconnect are we talking <BR>about here? Is there anything you can think of that would get extra data <BR>into the sockets? I don't think that a misconfiguration would lead to <BR>this particular behavior.<BR><BR>Rob<BR><BR>_______________________________________________<BR>PVFS-users mailing list<BR>PVFS-users@www.beowulf-underground.org<BR>http://beowulf-underground.org/mailman/listinfo/pvfs-users</BLOCKQUOTE></DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/">SBC Yahoo! DSL</a> - Now only $29.95 per month!
--0-1287780341-1058305907=:52786--