public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamil Kisiel <kamil@zymeworks.com>
To: xfs@oss.sgi.com
Subject: XFS and block-level snapshots
Date: Fri, 6 Jun 2008 11:33:17 -0700	[thread overview]
Message-ID: <FCF761C7-435E-4AA5-9055-9DA0033B7ACC@zymeworks.com> (raw)

Hello,

I had a question about XFS integrity and performing block-level  
snapshots.

We currently have a 2TB (but growing soon..) volume mounted by a Linux  
host with kernel 2.6.23 over iSCSI from our SAN. Our SAN unit has the  
capability to perform block-level snapshots, which is done at regular  
intervals.

I know that it is recommended to perform an xfs_freeze before  
performing a snapshot. However, the control of the snapshots is  
independent from the OS, which currently has no knowledge of their  
occurrence. I'm curious as to the repercussions of this. I understand  
that in all likelyhood, the integrity of files which are currently  
being written will not be preserved. However, even with an xfs_freeze  
this is not guaranteed, as an application may require additional disk  
transactions to maintain the file in a valid state (it is not  
necessarily atomic, depending on the application).

As far as metadata transactions are concerned, the journal should make  
these atomic, so there should not be any problem there?

Basically, I'd like to know what is the worst that could happen, and  
why an xfs_freeze is necessary in this scenario.

____________
Kamil Kisiel
HPC Systems Engineer, Zymeworks Inc.
201-1401 West Broadway,
Vancouver, BC, V6H 1H6, Canada
Tel: (604) 678-1388 ext. 135
Fax: (604) 737-7077
www.zymeworks.com

             reply	other threads:[~2008-06-06 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 18:33 Kamil Kisiel [this message]
2008-06-10  3:51 ` XFS and block-level snapshots Dave Chinner

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=FCF761C7-435E-4AA5-9055-9DA0033B7ACC@zymeworks.com \
    --to=kamil@zymeworks.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