Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Oct 2002 22:12:41 -0700
From:      David Schultz <dschultz@uclink.Berkeley.EDU>
To:        Matthew Dillon <dillon@apollo.backplane.com>
Cc:        Poul-Henning Kamp <phk@critter.freebsd.dk>, Maxim Sobolev <sobomax@FreeBSD.ORG>, hackers@FreeBSD.ORG
Subject:   Re: Patch to allow a driver to report unrecoverable write errors to the buf layer
Message-ID:  <20021020051241.GA24293@HAL9000.homeunix.com>
In-Reply-To: <200210200457.g9K4vbAE030661@apollo.backplane.com>
References:  <3DB048B5.21097613@FreeBSD.org> <28472.1035014051@critter.freebsd.dk> <20021020043706.GA23972@HAL9000.homeunix.com> <200210200457.g9K4vbAE030661@apollo.backplane.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Matthew Dillon <dillon@apollo.backplane.com>:
>     Extremely difficult, which is why this is all fantasy and no action.
>     By the time the filesystem layer gets the notification there is
>     insufficient information to unwind the original operation(s) without
>     a huge amount of work.  A bitmap write failed?  Great!  Find the 
>     file that the related bitmap blocks are related to.  Good luck!  And
>     that is just one case out of dozens that would require a sophisticated
>     solution.  It might be possible via softupdates, but I shudder at the
>     level of complexity of code required to support such a beast.  Not to
>     mention the fact that pulling a floppy out a bad time could destroy
>     far more data then whatever pending write operations might have failed.
>     It's a waste of time.

Then how about trying to solve a slightly easier problem?  When
the filesystem is forcibly unmounted, would it be possible to seek
out and destroy all busy buffers associated with it that couldn't
be written?  This isn't quite as nice a solution as getting the
system to automatically give up, but it's better than
necessitating a reboot to work around the problem.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021020051241.GA24293>