Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.os.vms Subject: Re: RX2800 sporadic disk I/O slowdowns Date: Sun, 20 Oct 2024 21:41:04 -0000 (UTC) Organization: A noiseless patient Spider Lines: 10 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sun, 20 Oct 2024 23:41:04 +0200 (CEST) Injection-Info: dont-email.me; posting-host="bebb5afd8d6b363c1d85744b8b6ba226"; logging-data="620414"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/D1xPQKaY5pkKwAdjg0qzi" User-Agent: Pan/0.160 (Toresk; ) Cancel-Lock: sha1:hUOT+X8d8gMYknRLhq2CmlpulgI= Bytes: 1693 On Sun, 20 Oct 2024 17:23:08 -0400, Arne Vajhøj wrote: > Loss of completed/committed data is the problem. The problem is not data loss, it is loss of data integrity. This is why we have transactions in databases and filesystems: on a crash or loss of power, we want transactions to be either completely lost or completely saved, not in some in-between incomplete state. There is no caching disk controller that knows how to ensure this.