Date: Mon, 31 May 1999 10:32:10 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Ustimenko Semen <semen@iclub.nsu.ru> Cc: Bruce Evans <bde@zeta.org.au>, freebsd-current@FreeBSD.ORG Subject: Re: How can i fail buf? Message-ID: <199905311732.KAA76108@apollo.backplane.com> References: <Pine.BSF.4.05.9905311917460.57028-100000@iclub.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
:On Mon, 31 May 1999, Bruce Evans wrote:
:
:> This isn't solved. It was less serious before rev.1.196 of vfs_bio.c
:> when B_ERROR buffers were discarded insead of re-dirtied in the above
:> code fragment. See also PR 11697, and about 20 PRs reporting problems
:> with i/o errors and EOF "errors" (ENOSPC/EINVAL) for (mis)using buffered
:> devices (especially fd0).
:>
:
:Why they have done so? B_ERROR have to mean unrecoverable
:error, doesn't it? Or we need something like
:
:Writing to ... at ... failed.
Generally the problem is that when a write fails, the buffer is not
invalid - it still contains perfectly valid data. We need a more
sophisticated mechanism to deal with I/O errors. Throwing away the
buffer (at least initially) is *not* the correct solution.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905311732.KAA76108>