Date: Wed, 03 Jan 1996 09:25:50 -0800 From: David Greenman <davidg@Root.COM> To: gpalmer@westhill.cdrom.com Cc: dfr@render.com, hackers@freebsd.org Subject: Re: 2.1 panic: panic: nfsreq nogrps Message-ID: <199601031725.JAA00438@corbin.Root.COM> In-Reply-To: Your message of "Wed, 03 Jan 96 04:26:22 PST." <10191.820671982@westhill.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>David Greenman wrote in message ID ><199601030538.VAA00222@corbin.Root.COM>: >> >in the origional mail), and I was just looking at the program which >> >was running at the time, and it does nothing more complicated than > >> The setgroups() can happen at any time and doesn't in itself cause a panic. >> The panic message "nfsreq nogrps" indicates that an I/O operation is being >> attempted on behalf of a process that has no groups in it's group list. This >> isn't a valid state as group[0] is always the effective gid. If the process >> didn't get this way because of setgroups(), then it's happening somewhere >> else in the kernel. I suppose one work-around kludge might be to substitute >> the "nobody" group (-2) for processes that otherwise belong to no groups. > >Look likes we'll need to do that as with a freshly updated copy of the >sources it just suffered the same panic again. Any idea why this is all-of-a-sudden happening regularly? -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601031725.JAA00438>