[pnfs] callback problem

William A. (Andy) Adamson andros at citi.umich.edu
Wed May 23 13:49:14 EDT 2007 

i'm working with just the sessions branch, and i cannot mount - the client
panics and the server segfaults! sheese.

has anybody else tried to run 4.1-sessions???

-->Andy

On 5/23/07, Iyer, Rahul <Rahul.Iyer at netapp.com> wrote:
>
> Hi Marc,
> Try this. Add the call to nfsd1_callback_probe back in. Unload the
> layoutdriver and try it. I have a feeling it might be on a
> create_session to the data servers.
> Regards
> Rahul
>
>
> > -----Original Message-----
> > From: Marc Eshel [mailto:eshel at almaden.ibm.com]
> > Sent: Wednesday, May 23, 2007 10:31 AM
> > To: Marc Eshel
> > Cc: pnfs at linux-nfs.org; pnfs-bounces at linux-nfs.org; Iyer, Rahul
> > Subject: Re: [pnfs] callback problem
> >
> > when I take out the call to nfsd41_probe_callback()
> > everything seems to work, but obviously we don't have
> > callback. I will try to see why this call failes.
> > Marc.
> >
> > pnfs-bounces at linux-nfs.org wrote on 05/23/2007 10:07:08 AM:
> >
> > > but even if the error msg is wrong the server crashes and this with
> > local
> > > mount that works for Benny.
> > >
> > > May 23 08:46:04 fin18 kernel: xxx server proc 43 May 23
> > 08:46:04 fin18
> > > kernel: NFSD: move_to_confirm nfs4_client f7ae6c00 May 23 08:46:04
> > > fin18 kernel: renewing client (clientid
> > 465461ab/00000001)
> > > May 23 08:46:04 fin18 kernel: NFSD:     looking up UNIX cred
> > > May 23 08:46:04 fin18 kernel: hash_sessionid IDX: 541 csum
> > 1883265350
> > > May 23 08:46:04 fin18 kernel: NFSD: nfs4_cb_null
> > task->tk_status 0 May
> > > 23 08:46:04 fin18 kernel: NFSD: callback set to client
> > 0.0.0.0 May 23
> > > 08:46:06 fin18 kernel: BUG: unable to handle kernel paging
> > request
> > > at virtual address 81ae0644
> > > May 23 08:46:06 fin18 kernel:  printing eip:
> > > May 23 08:46:06 fin18 kernel: f8c05665 May 23 08:46:06
> > fin18 kernel:
> > > *pde = 00000000 May 23 08:46:06 fin18 kernel: Oops: 0002
> > [#1] May 23
> > > 08:46:06 fin18 kernel: SMP May 23 08:46:06 fin18 kernel: Modules
> > > linked in: nfsd exportfs crc32
> > mmfs
> > > mmfslinux tracedev autofs4 nfs lockd sunrpc
> > >  tg3 ide_cd cdrom sg
> > > May 23 08:46:06 fin18 kernel: CPU:    1
> > > May 23 08:46:06 fin18 kernel: EIP:    0060:[<f8c05665>]
> > Not tainted
> > VLI
> > > May 23 08:46:06 fin18 kernel: EFLAGS: 00010286
> > (2.6.18.3-largeio-pnfs
> > > #2)
> > > May 23 08:46:06 fin18 kernel: EIP is at
> > > nfsd4_create_session+0x235/0x2c9
> >
> > > [nfsd]
> > > May 23 08:46:06 fin18 kernel: eax: 81ae0640   ebx: f7ae6c00   ecx:
> > > c33d6f4c   edx: f7ae6c28
> > > May 23 08:46:06 fin18 kernel: esi: 000010e8   edi: f7ae6d04   ebp:
> > > c33d6f40   esp: ef2bbe1c
> > > May 23 08:46:07 fin18 kernel: ds: 007b   es: 007b   ss: 0068
> > > May 23 08:46:07 fin18 kernel: Process nfsd (pid: 5038, ti=ef2ba000
> > > task=ef29dab0 task.ti=ef2ba000) May 23 08:46:07 fin18
> > kernel: Stack:
> > > ef090058 f7ae6c00 00200000 ef090050
> >
> > > f8c0cb1c 0000002b f6920bc0 f8bfc394
> > > May 23 08:46:07 fin18 kernel:        ef0a0000 ef090000
> > ef088000 f77a29c0
> >
> > > ef090050 f6920cc0 00000001 f7f2a000
> > > May 23 08:46:07 fin18 kernel:        0000000a 00000001
> > c011ee4e ef2bbe68
> >
> > > ef2bbe68 00000001 c03ba308 0000000a
> > > May 23 08:46:07 fin18 kernel: Call Trace:
> > > May 23 08:46:07 fin18 kernel:  [<f8bfc394>]
> > > nfsd4_proc_compound+0x12d1/0x14d1 [nfsd] May 23 08:46:07
> > fin18 kernel:
> > > [<c011ee4e>] run_timer_softirq+0x39/0x14f May 23 08:46:07 fin18
> > > kernel:  [<c011b4b9>] __do_softirq+0x5a/0xbb May 23 08:46:07 fin18
> > > kernel:  [<c0103267>]
> > apic_timer_interrupt+0x1f/0x24
> > > May 23 08:46:07 fin18 kernel:  [<c0117983>]
> > vprintk+0x286/0x2ba May 23
> > > 08:46:07 fin18 kernel:  [<c0110d01>]
> > __wake_up_common+0x2f/0x53 May 23
> > > 08:46:07 fin18 kernel:  [<c011113c>] __wake_up+0x2a/0x3d May 23
> > > 08:46:07 fin18 kernel:  [<f8a06e14>]
> > sunrpc_cache_lookup+0x5c/0xea
> > > [sunrpc]
> > > May 23 08:46:07 fin18 kernel:  [<f8bffae2>]
> > > nfs4svc_decode_compoundargs+0x0/0x50 [nfsd] May 23 08:46:07 fin18
> > > kernel:  [<f8bffa45>] nfsd4_decode_compound+0xd51/0xdee
> > [nfsd] May 23
> > > 08:46:07 fin18 kernel:  [<f8bffae2>]
> > > nfs4svc_decode_compoundargs+0x0/0x50 [nfsd] May 23 08:46:07 fin18
> > > kernel:  [<f8bee0cb>] nfsd_dispatch+0xbb/0x170 [nfsd] May
> > 23 08:46:07
> > > fin18 kernel:  [<f8a015f5>] svc_process+0x3b2/0x60d [sunrpc] May 23
> > > 08:46:07 fin18 kernel:  [<f8bee561>] nfsd+0x1aa/0x309 [nfsd] May 23
> > > 08:46:07 fin18 kernel:  [<f8bee3b7>] nfsd+0x0/0x309 [nfsd] May 23
> > > 08:46:07 fin18 kernel:  [<c0100bd1>]
> > kernel_thread_helper+0x5/0xb May
> > > 23 08:46:07 fin18 kernel: Code: 00 00 8d 9e 40 fa c1 f8 8b 86 40 fa
> > c1
> > > f8 89 50 04 89 45 04 89 5a 04 89 96 40 fa
> > > c1 f8 8b 54 24 04 83 c2 28 8b 5c 24 04 8b 43 28 <89> 48 04
> > 89 45 0c 89
> > 51
> > > 04 89 4b 28 31 db eb 0c 89 e8 e8 97 22 May 23 08:46:07
> > fin18 kernel:
> > > EIP: [<f8c05665>]
> > > nfsd4_create_session+0x235/0x2c9 [nfsd] SS:ESP 0068:ef2bbe1c
> > >
> > >
> > >
> > >
> > >
> > > "Iyer, Rahul" <Rahul.Iyer at netapp.com>
> > > 05/23/2007 09:47 AM
> > >
> > > To
> > > "Marc Eshel" <eshel at almaden.ibm.com>
> > > cc
> > > <pnfs at linux-nfs.org>
> > > Subject
> > > RE: [pnfs] callback problem
> > >
> > >
> > >
> > >
> > >
> > >
> > > Noo, no. That's not what I meant. All I'm saying is that you should
> > > ignore the IP address in the connect error message. I
> > should probably
> > > just fix the error.
> > >
> > > Callbacks should work.
> > > Thanks,
> > > Rahul
> > >
> > >
> > > > -----Original Message-----
> > > > From: Marc Eshel [mailto:eshel at almaden.ibm.com]
> > > > Sent: Wednesday, May 23, 2007 9:45 AM
> > > > To: Iyer, Rahul
> > > > Cc: pnfs at linux-nfs.org
> > > > Subject: RE: [pnfs] callback problem
> > > >
> > > > This is on the master branch. So is callback not expected to work
> > > > for now ?
> > > > Marc.
> > > >
> > > > "Iyer, Rahul" <Rahul.Iyer at netapp.com> wrote on 05/23/2007
> > 09:39:34 AM:
> > > >
> > > > > Is this the "master" branch or the 4.1-sessions branch? The
> > > > 0.0.0.0 is
> > > > > something I need to fix... The connection ip is
> > temporarily set to
> > > > > that as there is no need to connect.
> > > > > Thanks
> > > > > Regards
> > > > > Rahul
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Marc Eshel [mailto:eshel at almaden.ibm.com]
> > > > > > Sent: Wednesday, May 23, 2007 8:13 AM
> > > > > > To: pnfs at linux-nfs.org
> > > > > > Subject: [pnfs] callback problem
> > > > > >
> > > > > > Trying to mount from a pNFS client I get the following
> > > > trace on the
> > > > > > server and the client hangs. It looks like the
> > rpc_clnt was used
> > > > > > before it was initialized as you can tell from the
> > > > "nfs4_cb: server
> > > > > > 0.0.0.0" msg. Was anyone able to mount with the latest code ?
> > > > > > Marc.
> > > > > >
> > > > > > May 23 07:50:53 fin18 kernel: NFSD: move_to_confirm
> > nfs4_client
> > > > > > f6473400 May 23 07:50:53 fin18 kernel: renewing
> > client (clientid
> > > > > > 465454c2/00000001)
> > > > > > May 23 07:50:53 fin18 kernel: NFSD:     looking up UNIX cred
> > > > > > May 23 07:50:53 fin18 kernel: hash_sessionid IDX: 412 csum
> > > > > > 1587934240 May 23 07:50:54 fin18 kernel: nfsd4_create_session
> > > > > > returns 0 0 May 23 07:50:58 fin18 kernel: nfs4_cb: server
> > > > > > 0.0.0.0 not responding, timed out May 23 07:50:58 fin18
> > > > > > kernel: NFSD: nfs4_cb_null task->tk_status -5 May 23 07:50:59
> > > > > > fin18 kernel: NFSD: callback establishment to client
> > > > > > 9.1.72.239/9.1.72.227 AUTH_SYS 0 failed
> > > > > >
> > > > > > _______________________________________________
> > > > > > pNFS mailing list
> > > > > > pNFS at linux-nfs.org
> > > > > > http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
> > > > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > pNFS mailing list
> > > pNFS at linux-nfs.org
> > > http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
> >
> _______________________________________________
> pNFS mailing list
> pNFS at linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/pnfs/attachments/20070523/c0a3a63f/attachment-0001.htm

More information about the pNFS mailing list