DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I got an error message last week but didn't notice it until this week. I found it again in the kern.log.1 so I can report more details about what occurred immediately before and after. I haven't noticed any problems as a result, but then I'm not using the NFS service myself.
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (157)
nfsd: last server has exited
nfsd: unexporting all filesystems
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (157)
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
Should I do anything about this or just let it slide? It's happened just once in the last week.
What kind of network card are you using. I searched around and slummed around the netdev stuff and found little reference to this and even less useful replies to anyone reporting it. Seams like its a very obscure bug and might be related to a buggy controller driver. The kernel your using is a bit old and its possible a more recent kernel will clean it up depending on if your driver has had any cleanup work done. If its happening so rarely and not causing issues tho I would just ignore it and see if it goes away when a newer kernel is released.
That's what I thought. None of those replies seemed too useful to me either. It seemed to occur at a trivial moment though (when NFS was going to sleep for lack of users) and didn't recur when NFS came up later
It is possible that this issue is caused by several factors that are not easy to reproduce and as such has been overlooked by the kernel dev's. Its like trying to track down a car on a highway that only drives on sundays that have full moons and only on the 12th of the month :P
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.