mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Doug McNaught <doug@wireboard.com>
Cc: Lew Wolfgang <wolfgang@sweet-haven.com>, linux-kernel@vger.kernel.org
Subject: Re: Dump corrupts ext2?
Date: Wed, 10 Oct 2001 17:38:11 -0700	[thread overview]
Message-ID: <20011010173811.C3795@mikef-linux.matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110101558210.7049-100000@train.sweet-haven.com> <m3elob3xao.fsf@belphigor.mcnaught.org>
In-Reply-To: <m3elob3xao.fsf@belphigor.mcnaught.org>

On Wed, Oct 10, 2001 at 07:11:43PM -0400, Doug McNaught wrote:
> Lew Wolfgang <wolfgang@sweet-haven.com> writes:
> 
> > Hi Folks,
> > 
> > I was looking for some scripts to backup ext2 partitions
> > to multiple CDR's when I stumbled onto "cdbackup" at
> > http://www.cableone.net/ccondit/cdbackup/.
> > 
> > Alas, there is a warning saying:
> > 
> > "WARNING! When using this program under Linux, be sure not to use
> >  dump with kernels in the 2.4.x series. Using dump on an ext2
> >  filesystem has a very high potential for causing filesystem
> >  corruption.  As of kernel version 2.4.5, this has not been
> >  resolved, and it may not be for some time."
> > 
> > I don't recall any problems like this, does anyone have
> > additional comments?
> 
> 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).
>

IIRC, 2.2 didn't have a coherent buffer and page cache also.

I.E. if you "cat /dev/hda > /dev/null" you wouldn't be able to expect any
speedup when reading through the mounted filesystem (except for meta-data?).

Am I wrong?  Has Linux ever had a coherent page and buffer cache?

  parent reply	other threads:[~2001-10-11  0:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 23:03 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: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  2:57     ` H. Peter Anvin
2001-10-11  3:13       ` Andreas Dilger
2001-10-11  0:38   ` Mike Fedyk [this message]
2001-10-11  5:07     ` Eric W. Biederman
2001-10-11  1:33   ` Richard Gooch
2001-10-11  4:25     ` Richard Gooch
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=20011010173811.C3795@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=doug@wireboard.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

all inboxes | Powered by JetHome®