Date: Fri, 18 Oct 2002 13:16:40 -0400 From: Michael Lucas <mwlucas@blackhelicopters.org> To: sjs <sjs@mail2000.com.tw> Cc: freebsd-isp@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: NAS via NFS crashes with vinvalbuf: flush failed Message-ID: <20021018131640.A56728@blackhelicopters.org> In-Reply-To: <1034955118.86889.sjs@mail2000.com.tw>; from sjs@mail2000.com.tw on Fri, Oct 18, 2002 at 11:31:58PM %2B0800 References: <1034955118.86889.sjs@mail2000.com.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Could you prepare a debugging kernel, so people can get a better idea of what happens? If you need some hints, take a look at: http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html Various filesystem gurus will have a much better shot at figuring out the real problem if you have a dump on a debug kernel. Thanks! On Fri, Oct 18, 2002 at 11:31:58PM +0800, sjs wrote: > Hi, > > I have two FreeBSD servers mount NetApp NAS via NFS and run > under layer 4 switch to be redundant. I upgraded FreeBSD version > from 4.2R to 4.6.1-RC2, the panic crash still happen very often. > The messages I got from every crash are all the same which is about > "vinvalbuf: flush failed". Once the server-1 crashes, server-2 will > crash very soon. I guess there's some problems with accessing NFS > files on NAS, so when server-1 crashes, server-2 keeps accessing > the same file and then crahes, too. > > So is there any suggestion? Does it help to upgrade to 4.7R? > > PS: Both servers are with dual CPU with SMP enabled. I tried to > turn off SMP, but it didn't help anything. > > Thanks! > > Best regards, > Gareth > > ===========================Message attached===================== > > Oct 18 23:12:09 mail savecore: reboot after panic: vinvalbuf: flush failed > (kgdb) bt > #0 0xc01b0096 in dumpsys () > #1 0xc01afe67 in boot () > #2 0xc01b028c in poweroff_wait () > #3 0xc01dc4c9 in vinvalbuf () > #4 0xc023007c in nfs_vinvalbuf () > #5 0xc0252ee9 in nfs_open () > #6 0xc01e3943 in vn_open () > #7 0xc01df848 in open () > #8 0xc02e8aba in syscall2 () > #9 0xc02da2f5 in Xint0x80_syscall () > #10 0x804f62f in ?? () > #11 0x804d9f8 in ?? () > #12 0x804d2af in ?? () > #13 0x804cac1 in ?? () > #14 0x804adfc in ?? () > #15 0x804a289 in ?? () > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org http://www.oreillynet.com/pub/q/Big_Scary_Daemons Absolute BSD: http://www.AbsoluteBSD.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021018131640.A56728>