From: Dave Chinner <david@fromorbit.com>
To: aurfalien <aurfalien@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: LVM + XFS + external log + snapshots
Date: Mon, 24 Jun 2013 08:55:46 +1000 [thread overview]
Message-ID: <20130623225546.GB29376@dastard> (raw)
In-Reply-To: <022467CC-8EB2-41E9-8AF6-46F781882F6B@gmail.com>
On Fri, Jun 21, 2013 at 10:30:31PM -0700, aurfalien wrote:
> Hi all,
>
> So I have an XFS file system within LVM which has an external log.
>
> My mount option in FSTAB is;
>
> /dev/vg_spock_data/lv_data /data xfs logdev=/dev/sdc1,nobarrier,logbufs=8,noatime,nodiratime 1 1
>
> All is well no issues and very fast.
>
> Now I'd like to snapshot this bad boy and then run rsnapshot to create a few days backup.
You need to snapshot the log device as well.
But that is problematic in that you need to snapshot it at the same
time you snapshot the data volume. Hence yo'd have to do:
# xfs_freeze -f <filesystem>
# <snapshot data volume>
# <snapshot log volume>
# xfs_freeze -u <filesystem>
And now you can mount the snapshot with:
# mount /dev/vg_spock_data/datasnapshot /snapshot -o nouuid,ro,logdev=/dev/vg_spock_log/logsnapshot
If you can't snapshot the log device, then you can't snapshot the
filesystem. Yet another reason for using internal logs...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-23 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 5:30 LVM + XFS + external log + snapshots aurfalien
2013-06-22 7:58 ` Stan Hoeppner
2013-06-22 21:13 ` aurfalien
2013-06-23 22:55 ` Dave Chinner [this message]
2013-06-23 23:24 ` Eric Sandeen
2013-06-23 23:39 ` Dave Chinner
2013-06-24 0:33 ` aurfalien
2013-06-24 0:44 ` aurfalien
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=20130623225546.GB29376@dastard \
--to=david@fromorbit.com \
--cc=aurfalien@gmail.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