From: Lee Revell <rlrevell@joe-job.com>
To: Bernd Eckenfels <ecki-news2004-05@lina.inka.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: New concept of ext3 disk checks
Date: Thu, 12 Aug 2004 17:07:15 -0400 [thread overview]
Message-ID: <1092344835.1090.74.camel@mindpipe> (raw)
In-Reply-To: <E1BvKmO-0002dn-00@calista.eckenfels.6bone.ka-ip.net>
On Thu, 2004-08-12 at 14:58, Bernd Eckenfels wrote:
> I am not sure why the softupdates are so reliable, that no fsck is needed
Softupdates were introduced to enhance performance by batching and
deferring disk operations. I belive that initially, performance was the
only consideration in determining what actually got written to disk
when. All the BSD/OS manuals I read at my last job warn against
enabling softupdates because data loss could occur.
Someone later realized that if you batch the disk operations in a way
that considers the atomicity of the filesystem operations being
implemented, softupdates can help *ensure* data integrity. This is a
pretty recent development I think.
Lee
next prev parent reply other threads:[~2004-08-12 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 17:58 New concept of ext3 disk checks Otto Wyss
2004-08-12 18:58 ` Bernd Eckenfels
2004-08-12 21:07 ` Lee Revell [this message]
2004-08-12 19:46 ` Alan Cox
2004-08-14 7:26 ` Otto Wyss
2004-08-12 22:39 ` Theodore Ts'o
2004-08-12 23:55 ` Bernd Eckenfels
2004-08-13 0:34 ` Andreas Dilger
2004-08-14 7:15 ` Otto Wyss
2004-08-15 0:23 ` Andreas Dilger
[not found] <2ssbz-jB-1@gated-at.bofh.it>
[not found] ` <2swyz-3ny-13@gated-at.bofh.it>
2004-08-12 23:24 ` Andi Kleen
2004-08-12 23:48 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1092344835.1090.74.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=ecki-news2004-05@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.