Date: Tue, 07 Dec 1999 09:31:09 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Luoqi Chen <luoqi@watermarkgroup.com> Cc: jazepeda@pacbell.net, brian@CSUA.Berkeley.EDU, current@FreeBSD.ORG, vallo@matti.ee Subject: Re: mount(2) broken? Message-ID: <26461.944555469@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 07 Dec 1999 02:16:29 EST." <199912070716.CAA16646@lor.watermarkgroup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199912070716.CAA16646@lor.watermarkgroup.com>, Luoqi Chen writes: >I'd like to add something about the last buffer wouldn't sync. This occurs >when a shutdown syscall is issued when the syncer process is asleep waiting >for a buffer write to complete. The write will never complete, because the >syncer won't be given a chance to run again, and the buffer will stay marked >as busy and become the buffer that wouldn't sync. I haven't thought about >a clean way of handling this situation, maybe some of you out there have >better ideas... I always thought it would make sense to have the syncer perform the shutdown and cleanup since it had code to write buffers with anyway... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! 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?26461.944555469>