From: Doug McNaught <doug@wireboard.com>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: Lew Wolfgang <wolfgang@sweet-haven.com>, linux-kernel@vger.kernel.org
Subject: Re: Dump corrupts ext2?
Date: 10 Oct 2001 19:55:16 -0400 [thread overview]
Message-ID: <m33d4r3va3.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0110101558210.7049-100000@train.sweet-haven.com> <m3elob3xao.fsf@belphigor.mcnaught.org> <20011010173449.Q10443@turbolinux.com>
In-Reply-To: Andreas Dilger's message of "Wed, 10 Oct 2001 17:34:49 -0600"
Andreas Dilger <adilger@turbolabs.com> writes:
> On Oct 10, 2001 19:11 -0400, Doug McNaught wrote:
> > I'm pretty sure this is because dump reads the block device directly
> > (which is cached in the buffer cache), while the file data for cached
> > files lives in the page cache, and the two caches are no longer
> > coherent (as of 2.4).
>
> In Linus kernels 2.4.11+ the block devices and filesystems all use the
> page cache, so no more coherency issues.
You're right, of course. But for most of the lifetime of 2.4 the
above was true...
> Also, I don't think this ever had the potential to corrupt the filesystem,
> but maybe make a slightly bad backup.
Right, might corrupt the dump, but shouldn't hurt the filesystem.
-Doug
--
Let us cross over the river, and rest under the shade of the trees.
--T. J. Jackson, 1863
next prev parent reply other threads:[~2001-10-10 23:55 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 [this message]
2001-10-11 1:33 ` Richard Gooch
2001-10-11 1:48 ` Chris Mason
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=m33d4r3va3.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--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