Date: Tue, 17 Oct 2006 14:25:52 -0400 From: Vivek Khera <vivek@khera.org> To: stable@freebsd.org Subject: Re: nfsd stuck in ufs/biord/biowr/getblk Message-ID: <521F2F6A-17D5-4207-ABEE-549354311335@khera.org> In-Reply-To: <6eb82e0610171058k4f7ae15fqf797b1bd91b63faf@mail.gmail.com> References: <6eb82e0610161403n603aed79o6fed1df492504ef8@mail.gmail.com> <E1304C89-2DA7-40E9-9894-633798BFD77F@khera.org> <6eb82e0610171058k4f7ae15fqf797b1bd91b63faf@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 17, 2006, at 1:58 PM, Rong-en Fan wrote: > On 10/18/06, Vivek Khera <vivek@khera.org> wrote: >> >> On Oct 16, 2006, at 5:03 PM, Rong-en Fan wrote: >> >> > Yesterday, I saw my all my nfsd stuck in ufs/biord/biowr/getblk. >> > I saw the same thing some time ago. I break into ddb and do a >> > 'alltrace': >> >> do you have an em or bge ethernet? >> > > Yes. I do have an em0. My em0 does not share irq with other > device. I got watchdog timeout message every few days, but > I didn't get any in the deadlock above since boot. I have a box on which I had to replace the onboard bge with a 3com card since there was some interference between the bge and file system drivers causing total lockups during network use combined with heavy disk use. It was 100% reproducible by doing a level 0 dump on the nfs exported volume. My symptom was that the FFS would lockup that volume. If I got lucky, it would lock up the whole system and the only way out was via console debugger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?521F2F6A-17D5-4207-ABEE-549354311335>