# uname -a FreeBSD host.domain.tld 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 26 16:27:14 PST 2007 Greetings, Does anyone know when NFS and friends will be working again? I haven't been able to /safely/ use it from 4.8 on. I remember some talk on the list sometime ago and then it seemed to be resolved, as the discussion ended. So I thought it was fixed. Seems not. :( My scenario; mount host off root: mount script exec'd follows... #!/bin/sh - mount -t nfs host.domain.tld:/ /host mount -t nfs host.domain.tld:/var /host/var confirm mount... # ls /host .snap COPYRIGHT bin ... usr var tmp OK looks good... # cp /path/to/approx/10Mb/file /host/path/to/dest/dir/ Fatal double fault eis 0x0blah eiblah blah0x panic double fault no dump device defined rebooting in 15sec... Hmmm... that's not good. :( I can't remember all the "ei*" numbers between the Fatal and panic lines, BUT I /can/ reproduce this at will - I simply need to copy a file larger than a few k to a mounted host. Yes, this /does/ happen /every/ time. Any and all help with this will be /GREATLY/ appreciated. Thank you for all your time and consideration in this matter. --Chris -- panic: kernel trap (ignored) ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 /////////////////////////////////////////////////////////////////
Quoting Ruben van Staveren <ruben@verweg.com>:> Chris H. wrote: >> # uname -a >> FreeBSD host.domain.tld 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 26 >> 16:27:14 PST 2007 >> >> Greetings, >> Does anyone know when NFS and friends will be working again? I haven't >> been able >> to /safely/ use it from 4.8 on. I remember some talk on the list >> sometime ago and >> then it seemed to be resolved, as the discussion ended. So I thought >> it was >> fixed. Seems not. :( >> > >> >> # cp /path/to/approx/10Mb/file /host/path/to/dest/dir/ >> >> Fatal double fault >> eis 0x0blah >> eiblah blah0x >> panic double fault >> no dump device defined >> rebooting in 15sec... > > You might want to try to configure a dump device, or as a last resort, > take a picture of the crash and put that on your site >Greetings, and thank you for your reply. FWIW it was only 4 lines, each beginning with ei followed by their hex values. Like I said originally, I can crash it at will. If the "ei" lines make the difference, I can crash it and write them down. The values aren't that long. I hate to crash it, but it's crashed so many times while experimenting in an effort to find a way (KLUDGE) to get around it, I've got more salvaged inodes in lost+found than I have files on an entire FreeBSD install. Point being; if it /really/ makes the difference to have the "ei" values, I'll just crash it and record them to post here. It just seems that this /type/ of output would be an indicator to "those in the know" as to where I need to go about overcoming this - assuming it's on my end and not in the 6x i386/sys source. Thanks again.>> >> Hmmm... that's not good. :( >> >> I can't remember all the "ei*" numbers between the Fatal and panic lines, >> BUT I /can/ reproduce this at will - I simply need to copy a file larger >> than a few k to a mounted host. Yes, this /does/ happen /every/ time. >> >> Any and all help with this will be /GREATLY/ appreciated. >> >> Thank you for all your time and consideration in this matter. >> >> --Chris > > Regards, > Ruben >-- panic: kernel trap (ignored) ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 /////////////////////////////////////////////////////////////////
Chris H. wrote:> # uname -a > FreeBSD host.domain.tld 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 26 > 16:27:14 PST 2007 > > Greetings, > Does anyone know when NFS and friends will be working again? I haven't > been able > to /safely/ use it from 4.8 on. I remember some talk on the list > sometime ago and > then it seemed to be resolved, as the discussion ended. So I thought > it was > fixed. Seems not. :( >> > # cp /path/to/approx/10Mb/file /host/path/to/dest/dir/ > > Fatal double fault > eis 0x0blah > eiblah blah0x > panic double fault > no dump device defined > rebooting in 15sec...You might want to try to configure a dump device, or as a last resort, take a picture of the crash and put that on your site> > Hmmm... that's not good. :( > > I can't remember all the "ei*" numbers between the Fatal and panic lines, > BUT I /can/ reproduce this at will - I simply need to copy a file larger > than a few k to a mounted host. Yes, this /does/ happen /every/ time. > > Any and all help with this will be /GREATLY/ appreciated. > > Thank you for all your time and consideration in this matter. > > --ChrisRegards, Ruben
I have found that if I kill rpc.lockd on the NFS server, most of the NFS issues I have (including a similar lock-up on 6.1-RELEASE) go away. Just wanted to throw that "out there". - Dave Rivers -> > Greetings, > Does anyone know when NFS and friends will be working again? I haven't > been able > to /safely/ use it from 4.8 on. I remember some talk on the list > sometime ago and > then it seemed to be resolved, as the discussion ended. So I thought it was > fixed. Seems not. :( > > My scenario; > mount host off root: > mount script exec'd follows... > > #!/bin/sh - > mount -t nfs host.domain.tld:/ /host > mount -t nfs host.domain.tld:/var /host/var > > confirm mount... > > # ls /host > .snap COPYRIGHT bin > ... > usr var tmp > > OK looks good... > > # cp /path/to/approx/10Mb/file /host/path/to/dest/dir/ > > Fatal double fault > eis 0x0blah > eiblah blah0x > panic double fault > no dump device defined > rebooting in 15sec... > > Hmmm... that's not good. :( > > I can't remember all the "ei*" numbers between the Fatal and panic lines, > BUT I /can/ reproduce this at will - I simply need to copy a file larger > than a few k to a mounted host. Yes, this /does/ happen /every/ time. > > Any and all help with this will be /GREATLY/ appreciated. > > Thank you for all your time and consideration in this matter. > > --Chris > > > -- > panic: kernel trap (ignored) > > > > ----------------------------------------------------------------- > FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 > /////////////////////////////////////////////////////////////////
On Wed, Apr 04, 2007 at 01:43:46AM -0700, Chris H. wrote:> # uname -a > FreeBSD host.domain.tld 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 26 > 16:27:14 PST 2007 > > Greetings, > Does anyone know when NFS and friends will be working again?It works for the rest of us, so any problems you are seeing should be properly reported (this means you need a core dump + backtrace). However, since you have been having problems for so many years, but only on one machine, I would suspect hardware failure on your end. Kris -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070404/41b890df/attachment.pgp