public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Mario Becroft <mb@gem.win.co.nz>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Proper method of snapshotting XFS with external log using LVM2
Date: Wed, 1 Aug 2007 22:17:13 +1000	[thread overview]
Message-ID: <20070801121713.GY31489@sgi.com> (raw)
In-Reply-To: <1185737538.12064.44.camel@server.ak.quickcircuit.co.nz>

On Mon, Jul 30, 2007 at 07:32:18AM +1200, Mario Becroft wrote:
> I am using XFS and LVM2 under Linux. My XFS filesystems have an external
> log.
> 
> What is the correct method of creating an LVM2 snapshot of volumes
> containing an XFS filesystem with external log?

Not sure. I've never tried it.

> Do I need to snapshot the main filesystem volume and the log volume?

Yes.

> Should I be using xfs_freeze to ensure that the filesystem is not
> modified between when I create the filesystem snapshot and the log
> snapshot?

Yes.

> Or is there a special procedure for atomically creating both snapshots?
>
> Or should I not be using an external log? If not, won't this decrease
> performance?

If it doesn't work, then don't use an external log and yes, it will
decrease performance.

> In the past I have successfully used xfs_freeze and created separate
> snapshots of the filesystem and log volumes. However, I am not sure
> whether this is the recommended approach.

As long as both snapshots were taken with the one xfs_freeze command,
then it shouldbe ok.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-08-01 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29 19:32 Proper method of snapshotting XFS with external log using LVM2 Mario Becroft
2007-08-01 12:17 ` David Chinner [this message]
2007-08-01 12:23   ` Mario Becroft
2007-08-01 14:09     ` David Chinner
2007-08-01 15:02       ` Mario Becroft

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=20070801121713.GY31489@sgi.com \
    --to=dgc@sgi.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=mb@gem.win.co.nz \
    /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