public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Richard Bonomo <bonomo@sal.wisc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: backups/dumps/caches
Date: Wed, 7 Aug 2002 09:58:29 +1000	[thread overview]
Message-ID: <20020806235829.GF515@frodo> (raw)
In-Reply-To: <200208060032.g760WZP107993@maddog.sal.wisc.edu>

On Mon, Aug 05, 2002 at 07:32:34PM -0500, Richard Bonomo wrote:
> 
> Hello!
> 
> I have been trying to come up to speed on
> the issue of dumping file systems from
> 2.4.x kernels using dumps.  I located 
> Linus' unequivocal words about the dangers
> of using dump.   I have a couple of questions:
> 
> 1. Do the same warnings apply to XFS and xfsdump?

xfsdump doesn't directly access the device, so the metadata
and data it sees is coherent with other filesystem activity;
so, no these warnings are not applicable to xfsdump.

cheers.

-- 
Nathan

      parent reply	other threads:[~2002-08-06 23:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06  0:32 backups/dumps/caches Richard Bonomo
2002-08-06 20:54 ` backups/dumps/caches Oliver Xymoron
2002-08-06 22:34   ` backups/dumps/caches Alan Cox
2002-08-06 23:58 ` Nathan Scott [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=20020806235829.GF515@frodo \
    --to=nathans@sgi.com \
    --cc=bonomo@sal.wisc.edu \
    --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