This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Mon May 16 18:44:12 2022 Received: from spaans.ds9a.nl (adsl-xs4all.ds9a.nl [213.84.159.51]) by kylie.puddingonline.com (8.11.6/8.11.6) with SMTP id g8IG95X16182 for ; Wed, 18 Sep 2002 18:09:05 +0200 Received: (qmail 31894 invoked from network); 18 Sep 2002 07:10:09 -0000 Received: from unknown (HELO spaans.ds9a.nl) (3ffe:8280:10:360:202:44ff:fe2a:a1dd) by mayo.ipv6.ds9a.nl with SMTP; 18 Sep 2002 07:10:09 -0000 Received: (qmail 9780 invoked by uid 1000); 17 Sep 2002 20:46:40 -0000 Received: (maildatabase); juh Received: (qmail 11352 invoked by alias); 30 Nov 2001 17:22:27 -0000 Received: (qmail 11348 invoked from network); 30 Nov 2001 17:22:26 -0000 Received: from vger.kernel.org (::ffff:199.183.24.194) by spaans.ds9a.nl with SMTP; 30 Nov 2001 17:22:26 -0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 29 Nov 2001 11:07:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 29 Nov 2001 11:07:16 -0500 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]:62139 "EHLO zcars0m9.nortelnetworks.com") by vger.kernel.org with ESMTP id ; Thu, 29 Nov 2001 11:07:05 -0500 Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57]) by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fATG6Id08943 for ; Thu, 29 Nov 2001 11:06:18 -0500 (EST) Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com; Thu, 29 Nov 2001 11:06:57 -0500 Received: from zcard0k6.ca.nortel.com ([47.129.242.158]) by zcard015.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XRDZNN72; Thu, 29 Nov 2001 11:03:29 -0500 Received: from pcard0ks.ca.nortel.com ([47.129.117.131]) by zcard0k6.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XRF1DCG8; Thu, 29 Nov 2001 11:02:26 -0500 Received: from nortelnetworks.com (localhost.localdomain [127.0.0.1]) by pcard0ks.ca.nortel.com (Postfix) with ESMTP id 5621368A for ; Thu, 29 Nov 2001 11:07:12 -0500 (EST) Message-Id: <3C065D2F.B45332C6@nortelnetworks.com> Date: Thu, 29 Nov 2001 11:07:11 -0500 From: "Christopher Friesen" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.16 i686) X-Accept-Language: en Mime-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: logging to NFS-mounted files seems to cause hangs when NFS dies Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Orig: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org X-Spam-Tag: 1 Lines: 48 I'm working on an embedded platform and we seem to be having a problem with syslog and logging to NFS-mounted files. We have syslog logging to NFS and also logging to a server on another machine. The desired behaviour is that if the NFS server or the net connection conks out, the logs are silently dropped. (Critical logs are also logged in memory that isn't wiped out on reboot.) Currently, /var/log is mounted with the following options: rw,rsize=4096,wsize=4096,timeo=7,retrans=3,bg,soft,intr We started off with hard mounts due to the warnings about soft mounts, but that led to boxes totally hanging when the network connections were pulled or the NFS server was taken down. In this scenario we are even unable to login as root at the console. This forced us to go to soft mounts in an attempt to fix this behaviour. The problem we are seeing is that if we lose the network connection or the NFS mount (which immediately causes an attempt to log the problem), it seems that syslog gets stuck in NFS code in the kernel and other stuff can be delayed for a substantial amount of time (many tens of seconds). Just for kicks we tried logging to ramdisk, and everything works beautifully. Now I'm a bit unclear as to why other processes are being delayed--does anyone have any ideas? My current theories are that either the nfs client code has a bug, or syslog() calls are somehow blocking if syslogd can't write the file out. I've just started looking at the syslog code, but its pretty rough going as there are very few comments. Help? We're running a customized 2.2.17 kernel and syslog 1.4.1. Thanks, Chris Friesen -- Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/