From: Michael Sinz <msinz@wgate.com>
To: Ganajyoti Bhattacherjee <bgana@cmie.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Data Corruption with Dump
Date: Mon, 20 May 2002 08:03:15 -0400 [thread overview]
Message-ID: <3CE8E603.8010205@wgate.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205201708170.3638-100000@saturn.cmie.ernet.in>
Ganajyoti Bhattacherjee wrote:
> I just happenned to read Linus'opinion on using dump for backup (in a
> mail from him to linux-kernel mailing list on 27 Apr 2001). He wrote
>
> -------------------------------------------------------------------------
> "...Note that dump simply won't work reliably at all even in 2.4.x: the
> buffer cache and the page cache (where all the actual data is) are not
> coherent. This is only going to get even worse in 2.5.x, when the
> directories are moved into the page cache as well.
>
> So anybody who depends on "dump" getting backups right is already playing
> russian rulette with their backups. It's not at all guaranteed to get the
> right results - you may end up having stale data in the buffer cache that
> ends up being "backed up"......"
> ---------------------------------------------------------------------------
>
> But is the above true even in case of taking "dump" of an unmounted
> filesystem.
No - this was written about mounted filesystems. Since dump does not go
through the VFS layer and thus does not go through the buffer cache, it
will miss things in an active filesystem. In a filesystem that is not
mounted (I assume cleanly unmounted) there would be no problem. To me,
the issue of dump is that it really does not work on a always-up system.
I can not just take the system off-line to backup so the backup mechanisms
I use are all via the file system layer and thus work with the VFS and
page cache and buffer cache rather than around them...
--
Michael Sinz ---- Worldgate Communications ---- msinz@wgate.com
A master's secrets are only as good as
the master's ability to explain them to others.
prev parent reply other threads:[~2002-05-20 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 11:40 Data Corruption with Dump Ganajyoti Bhattacherjee
2002-05-20 12:03 ` Michael Sinz [this message]
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=3CE8E603.8010205@wgate.com \
--to=msinz@wgate.com \
--cc=bgana@cmie.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox