From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <9d6d136fb79aaf185e80671ff96927d9@pi.att> References: <20130602155946.GA76076@intma.in> <17f847d4bb447895848cd56daccb4d7b@proxima.alt.za> <20130602165344.GA92436@intma.in> <914e8aff703ae3592f13e3fa53a2c23f@kw.quanstro.net> <20130603114926.GA19716@intma.in> <70f065b39c27bd8063d14eef751cecb8@brasstown.quanstro.net> <9d6d136fb79aaf185e80671ff96927d9@pi.att> Date: Mon, 3 Jun 2013 20:27:33 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b624d74d45a1f04de44f45e Subject: Re: [9fans] Fossil disk usage over 100%? Topicbox-Message-UUID: 62af9ac2-ead8-11e9-9d60-3106f5b1d025 --047d7b624d74d45a1f04de44f45e Content-Type: text/plain; charset=UTF-8 On 3 June 2013 16:45, wrote: > Saying "there is no problem" changes nothing. You can > debate with the Grand Canyon for hours, but when you walk off the > cliff you're still going to plummet to the ground. > No doubt, but you then do then *exactly* the same thing with cwfs. To my certain knowledge, it is possible for the old file server to lose data and files, sometimes catastrophically so, forcing a recover main, and sometimes, a recover further back. That's unsurprising if you look at the code. It's easy to fix by making it really, really slow at writing. And even then, your drives will have buffered the data and not written it. There's a good reason my file servers were on UPS. Even that isn't guaranteed, because notoriously, you'll find the UPS battery has gone just when you need it. --047d7b624d74d45a1f04de44f45e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 3 June 2013 16:45, <sl@9front.org> wrote:
Saying "there is no problem= " changes nothing. You can
debate with the Grand Canyon for hours, but when you walk off the
cliff you're still going to plummet to the ground.

No doubt, but you then do then *exactly* the same thing with cwfs.<= /div>
To my certain knowledge, it is possib= le for the old file server to lose
data and files, sometimes catastrophically= so, forcing a recover main,
and some= times, a recover further back. That's unsurprising if you look
at the code. It's easy to fix by making it really, really slow at writi= ng.
And even then, your drives will h= ave buffered the data and not written it.
There's a good reason my file servers were on UPS.
Even that isn't guaranteed, because notoriously, you&= #39;ll find the UPS battery has gone
just when you need it.

--047d7b624d74d45a1f04de44f45e--