From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Tolpin Message-Id: <200405140859.i4E8x4T0066071@adat.davidashen.net> Subject: Re: [9fans] disk/^(mbr format fdisk prep) In-Reply-To: <3da71b1c3631431f81d31e9eab88b528@granite.cias.osakafu-u.ac.jp> To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Date: Fri, 14 May 2004 13:59:04 +0500 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Topicbox-Message-UUID: 7ab258f4-eacd-11e9-9e20-41e7f4b1d025 Kenji Okamoto: > > I don't fully understand the concern. Right now, mini-box with CF and fossil > > (without venti) on it is my only Plan 9 machine, standalone cpu+file server+auth. > > What's wrong with fossil for that? > > Because none sayes about unstability of Ken's fs or kfs, but some do for > fossil things. Of course some of them should be from wrong usage of it. > However, I can't have confidnce that it's stable enough for our site. I am saying about instability of kfs. I am getting the same bug on several different computers, unless a fix is applied. When kfs is rebooted after power failure, it reports wrenwrite errors in endless loop. The fix is to flush dirty blocks to disk after checking and reparing and before kfs is launched. The fix is simple, but the problem is that I can't understand why it matters. It is a race, if enough debuggin output is added, the bug disappears due to accidental slowdown. Everyone has UPSes these days, so people just don't notice. Not everyone lives in a region when blackouts last for hours occasionally. David