linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: David Brown <david@westcontrol.com>
Cc: CoolCold <coolthecold@gmail.com>,
	keld@keldix.com, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: XFS on top RAID10 with odd drives count and 2 near copies
Date: Tue, 14 Feb 2012 05:10:27 -0600	[thread overview]
Message-ID: <4F3A4123.1050508@hardwarefreak.com> (raw)
In-Reply-To: <4F3A23F1.6090908@westcontrol.com>

On 2/14/2012 3:05 AM, David Brown wrote:

> I believe that if you have XFS on LVM, then making a snapshot will first
> "freeze" the filesystem, take the snapshot, then "thaw" the filesystem.
>  This process will sync the system, flushing out outstanding writes, and
> delay new writes until the "thaw" - thus you get a bit better than a
> "power-off copy".  In particular, you don't get zeroed-out files no
> matter what you've done with your barrier settings.

xfs_freeze[1] was a feature/command carried over from IRIX to Linux
during the XFS port.  This functionality was later moved from the XFS
layer into the VFS layer.  Now FS freezing is fully automatic when an
LVM snapshot is taken.  Now in the VFS layer, this works with any
filesystem type, EXT2/3/4, Reiser, JFS, XFS.  I don't have the date or
kernel rev handy where this was integrated in mainline.  It's been at
least a couple/few years.  I'm not inclined to dig it up.


[1] xfs_freeze(8)

NAME
       xfs_freeze - suspend access to an XFS filesystem

SYNOPSIS
       xfs_freeze -f | -u mount-point

DESCRIPTION
       xfs_freeze suspends and resumes access to an XFS filesystem (see
xfs(5)).
[...]


-- 
Stan

  reply	other threads:[~2012-02-14 11:10 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 15:17 XFS on top RAID10 with odd drives count and 2 near copies CoolCold
2012-02-11  4:05 ` Stan Hoeppner
2012-02-11 14:32   ` David Brown
2012-02-12 20:16   ` CoolCold
2012-02-13  8:50     ` David Brown
2012-02-13  9:46       ` CoolCold
2012-02-13 11:19         ` David Brown
2012-02-13 13:46       ` Stan Hoeppner
2012-02-13  8:54     ` David Brown
2012-02-13  9:49       ` CoolCold
2012-02-13 12:09     ` Stan Hoeppner
2012-02-13 12:42       ` David Brown
2012-02-13 14:46         ` Stan Hoeppner
2012-02-13 21:40       ` CoolCold
2012-02-13 23:02         ` keld
2012-02-14  3:49           ` Stan Hoeppner
2012-02-14  8:58             ` David Brown
2012-02-14 11:38             ` keld
2012-02-14 23:27               ` Stan Hoeppner
2012-02-15  8:30                 ` Robin Hill
2012-02-15 13:30                   ` Stan Hoeppner
2012-02-15 14:03                     ` Robin Hill
2012-02-15 15:40                     ` David Brown
2012-02-17 13:16                       ` Stan Hoeppner
2012-02-17 14:57                         ` David Brown
2012-02-17 19:30                           ` Peter Grandi
2012-02-18 13:59                             ` David Brown
2012-02-19 14:46                           ` Peter Grandi
2012-02-17 19:03                         ` Peter Grandi
2012-02-17 22:12                           ` Stan Hoeppner
2012-02-18 17:09                           ` Peter Grandi
2012-02-15  9:24                 ` keld
2012-02-15 12:10                 ` David Brown
2012-02-15 13:08                   ` keld
2012-02-17 18:44                 ` Peter Grandi
2012-02-18 17:39                   ` Peter Grandi
2012-02-14  7:31           ` CoolCold
2012-02-14  9:05             ` David Brown
2012-02-14 11:10               ` Stan Hoeppner [this message]
2012-02-14  2:49         ` Stan Hoeppner

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=4F3A4123.1050508@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=coolthecold@gmail.com \
    --cc=david@westcontrol.com \
    --cc=keld@keldix.com \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).