[PVFS2-users] Fedora Core 2 (AMD64) w/ v0.6.4 kernel modules

[Michael Hanulec]

Hi..

/*
Base OS: Fedora Core 2 for x86_64/AMD64, updated fully.
Kernel: 2.6.8-1.521smp
PVFS2 release: 0.6.4
*/

I'm having some problems getting pvfs2-client and the mounting of file 
systems to work reliabily.  I've been reading the mailing list, but 
haven't seen these exact errors.  The pvfs2-ping, pvfs2-ls, pvfs2-cp 
utilities all work 100%.  This is my first PVFS2 install.. so I will 
appologize for all of my mistakes now :).  I've tried re-compiling the 
source code twice in /usr/src but have receive the errors both times. 
These kernel errors occur if I have one or more IO servers.

Does anyone have any suggestions as to what is going on below?

Has anyone successfully gotten Fedora Core 2 for AMD64 to work w/ PVFS2??

Thanks!

-Mike

[root at node08 root]# pvfs2-client -f -V
pvfs2-client starting
Spawning new child process
Waiting on child with pid 2957
About to exec pvfs2-client-core

Message from syslogd at node08 at Thu Sep  9 13:07:34 2004 ...
node08 kernel: invalid operand: 0000 [1] SMP
[root at node08 root]#



<begin dmesg output from node08>
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at fork:120
invalid operand: 0000 [1] SMP
CPU 0
Modules linked in: pvfs2(U) md5 ipv6 parport_pc lp parport autofs4 nfs 
lockd ds yenta_socket pcmcia_core sunrpc e1000 floppy sg scsi_mod dm_mod 
ohci_hcd ext3 jbd
Pid: 2957, comm: pvfs2-client-co Not tainted 2.6.8-1.521smp
RIP: 0010:[<ffffffff80136411>] <ffffffff80136411>{add_wait_queue+50}
RSP: 0018:000001003adb1e48  EFLAGS: 00010016
RAX: 0000000000000016 RBX: ffffffffa01ac1c0 RCX: ffffffff8040a8a8
RDX: ffffffff8040a8a8 RSI: 0000000000000001 RDI: 000001003c4c9490
RBP: 000001003cd3e018 R08: ffffffff8040a8a8 R09: 0000000100000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000010037f354ac
R13: 0000000000000000 R14: 000001003adb1eec R15: 000001003adb1ee0
FS:  0000002a95567e20(0000) GS:ffffffff804e2d80(0000) 
knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000003e1d7b2370 CR3: 0000000000101000 CR4: 00000000000006e0
Process pvfs2-client-co (pid: 2957, threadinfo 000001003adb0000, task 
000001003c4c9490)
Stack: 0000000000000246 0000000000000000 0000000000000145 0000000000000000
        0000000000000145 ffffffffa01a2640 000001003fb96c80 ffffffff80190ee8
        000001007f354268 0000010037f354ac
Call Trace:<ffffffffa01a2640>{:pvfs2:pvfs2_devreq_poll+28} 
<ffffffff80190ee8>{do_pollfd+108}
        <ffffffff80190f83>{do_poll+88} <ffffffff8019114b>{sys_poll+346}
        <ffffffff801904fc>{__pollwait+0} 
<ffffffff801115b6>{system_call+126}


Code: 0f 0b 9a 94 33 80 ff ff ff ff 78 00 f0 fe 0b 0f 88 f6 21 00
RIP <ffffffff80136411>{add_wait_queue+50} RSP <000001003adb1e48>
  *****************************************************
PVFS2 Device Error:  You cannot open the device file
/dev/pvfs2-req more than once.  Please make sure that
there are no instances of a program using this device
currently running. (You must verify this!)
For example, you can use the lsof program as follows:
'lsof | grep pvfs2-req' (run this as root)
   open_access_count = 1
*****************************************************
.....

</end dmesg output from node08>



<dmesg output from 'master', which has been configured as the meta and io 
server too>
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at semaphore:120
invalid operand: 0000 [11] SMP
CPU 1
Modules linked in: nfsd exportfs lockd pvfs2(U) parport_pc lp parport 
autofs4 ds yenta_socket pcmcia_core sunrpc iptable_filter ip_tables e1000 
floppy sg md5 ipv6 dm_mod ohci_hcd ext3 jbd 3w_9xxx mptscsih mptbase 
sd_mod scsi_mod
Pid: 4861, comm: mount Not tainted 2.6.8-1.521smp
RIP: 0010:[<ffffffff80317a0b>] <ffffffff80317a0b>{__down_interruptible+96}
RSP: 0018:0000010079843c78  EFLAGS: 00010016
RAX: 0000000000000016 RBX: ffffffffa019b180 RCX: ffffffff8040a8a8
RDX: ffffffff8040a8a8 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffffffa019b180 R08: ffffffff8040a8a8 R09: 0000000100000000
R10: 0000000000000000 R11: 0000000000000000 R12: 000001002dbed3d0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS:  0000002a955714c0(0000) GS:ffffffff804e2e00(0000) 
knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000617000 CR3: 0000000001e32000 CR4: 00000000000006e0
Process mount (pid: 4861, threadinfo 0000010079842000, task 
000001002dbed3d0)
Stack: 0000000000000216 ffffffff80161931 000001007ffd095c 000000d000000010
        0000000000000000 000001002dbed3d0 ffffffff801346a8 0000000000000000
        0000000000000000 000001003ce739c8
Call Trace:<ffffffff80161931>{cache_grow+352} 
<ffffffff801346a8>{default_wake_function+0}
        <ffffffff803192b3>{__down_failed_interruptible+53}
        <ffffffffa0193f12>{:pvfs2:.text.lock.super+89} 
<ffffffff8019a87c>{find_filesystem+37}
        <ffffffff80183768>{do_kern_mount+161} 
<ffffffff8019c58d>{do_new_mount+96}
        <ffffffff8019ce52>{do_mount+371} 
<ffffffff8015d0e6>{__get_free_pages+13}
        <ffffffff8019d244>{sys_mount+232} 
<ffffffff801115b6>{system_call+126}


Code: 0f 0b d0 3f 33 80 ff ff ff ff 78 00 f0 fe 4d 08 0f 88 8f 01
RIP <ffffffff80317a0b>{__down_interruptible+96} RSP <0000010079843c78>
</end of dmesg output from master node>


--
hanulec at hanulec.com		cell: 858.518.2647 && 516.410.4478
https://secure.hanulec.com	      EFnet irc && aol im: hanulec