public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Olaf Frączyk" <olaf@cbk.poznan.pl>
To: Timothy Shimmin <tes@sgi.com>
Cc: Leon Kolchinsky <leonk@construct.haifa.ac.il>, xfs@oss.sgi.com
Subject: Re: xfsdump/xfsrestore question
Date: Thu, 22 Feb 2007 13:48:17 +0100	[thread overview]
Message-ID: <1172148497.4634.36.camel@venus.local.navi.pl> (raw)
In-Reply-To: <80FFF742E8A3FFB101CF1455@timothy-shimmins-power-mac-g5.local>

On Wed, 2007-02-21 at 11:07 +1100, Timothy Shimmin wrote:
> Hi,
> 
> --On 20 February 2007 4:16:31 PM +0200 Leon Kolchinsky <leonk@construct.haifa.ac.il> wrote:
> 
> > Hello All,
> >
> > I have a question about xfsdump/xfsrestore usage on Linux.
> >
> > Now the questions:
> >
> > 1) If I get the xfsdump synax correctly I just have to do:
> >
> ># cd /
> ># xfsdump -f /data/backup.file /
> >
> > Is it right?
> > What about opened and "currently in use by the system" files? Are they
> > backuped in a proper way? What about tmpfs like /proc, are they been
> > ignored?
> >
(...)
> Yes it is meant to handle a changing filesystem - you do see warning msgs sometimes because
> it can't see a particular inode anymore, which can happen as we do multiple
> scans of the inodes and if they get deleted then it obviously can't do anything
> with it anymore or if the inode is reused as a dir instead of a reg-file etc...
Hmm,
I suppose he asked about something else:
Unless you use lvm snapshots (or something alike) you may get incorrect
files that are in use. Consider having 20GB file:
1. Dump starts reading the file
2. Dump is at 18th GB
3. You change the data in 1-5 GB region.
4. You have inconsistent data.

So after dump you get consistent filesystem but not necessairly
consistent data.

Regards,

Olaf

-- 
Olaf Frączyk <olaf@cbk.poznan.pl>

  parent reply	other threads:[~2007-02-22 13:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20 14:16 xfsdump/xfsrestore question Leon Kolchinsky
2007-02-20 14:19 ` Justin Piszcz
2007-02-21  0:07 ` Timothy Shimmin
2007-02-21 21:02   ` Leon Kolchinsky
2007-02-22 12:48   ` Olaf Frączyk [this message]
2007-02-24 15:04     ` Leon Kolchinsky
2007-02-24 15:10       ` Iustin Pop
2007-02-26 13:14         ` Leon Kolchinsky
2007-02-26  5:29       ` Donald Douwsma
2007-02-26  5:52       ` Timothy Shimmin
2007-02-26 13:16         ` Leon Kolchinsky

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=1172148497.4634.36.camel@venus.local.navi.pl \
    --to=olaf@cbk.poznan.pl \
    --cc=leonk@construct.haifa.ac.il \
    --cc=tes@sgi.com \
    --cc=xfs@oss.sgi.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