From owner-freebsd-hackers Tue Dec 18 4:34:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chmls18.ne.ipsvc.net (chmls18.ne.ipsvc.net [24.147.1.153]) by hub.freebsd.org (Postfix) with ESMTP id F28EE37B41A for ; Tue, 18 Dec 2001 04:34:31 -0800 (PST) Received: from gandalf (h00045ae37142.ne.mediaone.net [65.96.123.237]) by chmls18.ne.ipsvc.net (8.11.6/8.11.6) with SMTP id fBICYTG19624 for ; Tue, 18 Dec 2001 07:34:29 -0500 (EST) Message-ID: <00ab01c187c0$53ac5cc0$6401a8c0@gandalf> From: "Dragon Fire" To: Subject: Re: deadlock with softupdates ? Date: Tue, 18 Dec 2001 07:34:19 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG We saw something very similar to this about a year using FFS and soft updates when we were building a NAS appliance. The details escape me and I no longer work the company so I cannot grep the source code but here's what I remember. The softupdate code periodically flushes the meta data. There is a flag in the soft update code that periodically sets a flag to starts the meta data flush timer. There was a condition in which this flag was not set properly causing FFS to freeze, in particular with NFS running. Hope this helps. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message