From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1814230b714601cd6e55fdc37232f6a3@quanstro.net> From: erik quanstrom Date: Fri, 8 May 2009 12:39:31 -0400 To: 9fans@9fans.net In-Reply-To: <181f918ef3641b854a5fcd822a1973e5@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] cwfs Topicbox-Message-UUID: f6a94a92-ead4-11e9-9d60-3106f5b1d025 > used the cphist program from http://www.quanstro.net/plan9/history.pdf > and wrote a /dev/(bin)time faking fileserver > (/n/sources/contrib/cinap_lenrek/delorean) that fools cwfs and replica > about the current time, but does not confuse cron and fossil. you very sneaky! i love it. thanks for the write up. > cwfs needs to be halted correctly as it has no jurnaling or softupdates. mmm. i have not had any trouble with unexpected shutdowns. and i have had a few. maybe not enough. i could have just been lucky, but i suspect that ken was much craftier than that. i suspect, but haven't taken the time to verify, that ken rolls up to the root so while one may write unfinished garbage to the cache device, you won't see corruption. unless your fancy disk has reorderd writes in a bad way. :-) you may wish to take the change that the diskless fs code has to the cache on-disk layout. by going column wise one can eliminate the seek between every successive block. you will need a cache big enough to never resize. what you give up is the ability to add cache during startup. (is there even a console at startup with cwfs?) - erik