From owner-freebsd-hackers Thu Aug 24 17:38:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 3F85737B424 for ; Thu, 24 Aug 2000 17:38:34 -0700 (PDT) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id UAA08757 for ; Thu, 24 Aug 2000 20:38:30 -0400 (EDT) Date: Thu, 24 Aug 2000 20:35:14 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: delayed write question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am wondering what exactly will happen if a delayed write goes wrong. It seems to me that the kernel will just clear the error flag and mark the buffer as delayed write again. This gives the buffer a second chance. But how many chances at most a buffer can get before it is aborted. While this may seem not serious on a local filesystem. Consider the NFS case, if a delayed write to a NFS server fails, how many times will we retry? My understanding is that the user program will not notice these retries or aborts until it closes the file. Am I right? Please clarify this for me. Before 4.0, if we write something to a write-protected floppy, the system will panic. Obviously, this panic does not happen on 4.0+. So I guess that the retries must have a limit. Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message