From: Stan Hoeppner <stan@hardwarefreak.com>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: LVM + XFS + external log + snapshots
Date: Sat, 22 Jun 2013 02:58:16 -0500 [thread overview]
Message-ID: <51C55918.1030004@hardwarefreak.com> (raw)
In-Reply-To: <022467CC-8EB2-41E9-8AF6-46F781882F6B@gmail.com>
Sorry for err aurfalien, first reply didn't make the list.
On 6/22/2013 12:30 AM, aurfalien wrote:
> Hi all,
>
> So I have an XFS file system within LVM which has an external log.
Migrate to internal logs as snaps are easy. Since delaylog (2.6.39+)
external logs are generally no longer needed, provide little to no
advantage as log bandwidth drops dramatically. If RHEL or CentOS that's
6.2 or later.
...
> lvcreate -L250G -s -n datasnapshot /dev/vg_spock_data/lv_data
>
> But when i try to mount the file system;
For now, to get past this current problem, you must snapshot both the
filesystem and the log, during the same freeze. You're currently
cloning the Lone Ranger without cloning Tonto. Ain't gonna work. And
it looks like the log device doesn't reside on LVM, so you're outta
luck, can't snap it.
> logdev=/dev/sdc1
> Am I doing something wrong or is this not possible?
Your first error was putting the log on raw storage instead of an LV.
If your kernel is new enough to support delaylog, then your 2nd error
was using an external log. External logs were once useful for high
metadata workloads, but since delaylog they are largely no longer needed.
xfsdump the filesytem, mkfs.xfs with an internal log, then xfsrestore.
Alternatively you could keep the external log: Remount the live XFS
using an alternate location for the log. Put an LV on sdc1. Then
remount again using this new LV as the log location. Then you can snap
both XFS and the log, and mount the snap with the matching log.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-22 7:58 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 [this message]
2013-06-22 21:13 ` aurfalien
2013-06-23 22:55 ` Dave Chinner
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=51C55918.1030004@hardwarefreak.com \
--to=stan@hardwarefreak.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