From: Chris Mason <mason@suse.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>,
Andreas Dilger <adilger@turbolabs.com>
Cc: Doug McNaught <doug@wireboard.com>,
Lew Wolfgang <wolfgang@sweet-haven.com>,
linux-kernel@vger.kernel.org
Subject: Re: Dump corrupts ext2?
Date: Wed, 10 Oct 2001 21:48:41 -0400 [thread overview]
Message-ID: <1160370000.1002764921@tiny> (raw)
In-Reply-To: <200110110133.f9B1XtN28012@vindaloo.ras.ucalgary.ca>
In-Reply-To: LINKIFYbBIcAACHFaJdeIDaaacJbIFEbCEFfeDAEIDdGJFfLINKIFYJDAJFFGcIdHbDEcDHDDDdGEacfDCEcJHdecDCEDCLINKIFYEFaHfBeAFGBabdeABfCabdJGcfaHfaEDaAeHedcC <200110110133.f9B1XtN28012@vindaloo.ras.ucalgary.ca>
On Wednesday, October 10, 2001 07:33:55 PM -0600 Richard Gooch <rgooch@ras.ucalgary.ca> wrote:
> Andreas Dilger writes:
>> In Linus kernels 2.4.11+ the block devices and filesystems all use
>> the page cache, so no more coherency issues.
>
> Um, I thought that there wasn't going to be coherency? For example, if
> you open /dev/sda and /dev/sda1, they each have a separate cache. I
> remember some debate about this, and Linus pointed out how hard it was
> to make things coherent.
They all use the page cache, but they still use different address spaces.
The block device and getblk share the same address space, so the metadata
and the block device are on the same cache, except for ext2 directories,
which act like files do. Each file has its own address space, so that
isn't coherent with the block device.
In other words, block device reads with the FS mounted will probably
never give consistent results.
The bug where dump could corrupt things was when getblk and the
block device both used the buffer cache. That issue hasn't changed.
-chris
next prev parent reply other threads:[~2001-10-11 1:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 23:03 Dump corrupts ext2? Lew Wolfgang
2001-10-10 23:11 ` Doug McNaught
2001-10-10 23:34 ` Andreas Dilger
2001-10-10 23:55 ` Doug McNaught
2001-10-11 1:33 ` Richard Gooch
2001-10-11 1:48 ` Chris Mason [this message]
2001-10-11 4:16 ` Benjamin LaHaise
2001-10-11 4:29 ` Alexander Viro
2001-10-11 11:47 ` Chris Mason
2001-10-11 4:25 ` Richard Gooch
2001-10-11 2:57 ` H. Peter Anvin
2001-10-11 3:13 ` Andreas Dilger
2001-10-11 0:38 ` Mike Fedyk
2001-10-11 5:07 ` Eric W. Biederman
2001-10-10 23:28 ` H. Peter Anvin
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=1160370000.1002764921@tiny \
--to=mason@suse.com \
--cc=adilger@turbolabs.com \
--cc=doug@wireboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--cc=wolfgang@sweet-haven.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox